[MGNLUI-511] page editor: links inside page editor on webkit and location change Created: 19/Sep/12  Updated: 25/Apr/14  Resolved: 10/Jan/13

Status: Closed
Project: Magnolia UI
Component/s: page editor
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Bug Priority: Critical
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLUI-505 Page editor iframe hangs on reloading... Closed
relation
is related to MAGNOLIA-4488 When navigations are moved in an area... Closed
is related to MGNLUI-2744 Page editor: all links outside of nav... Closed
is related to MGNLUI-534 Page Editor: when browsing inside pag... Closed
is related to MGNLUI-2746 pages app doesn't catch all page changes Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Currently a page change inside the page editor is not properly detected on webkit, due to problems with onload event in the iframe.
One possible solution in combination with SCRUM-4488 would be to not skip elements inside a navigation-div but rather to register an callback to the links. That callback would then trigger the poller on the readystate of the iframe and reinitialize the page editor.

When navigating to a new page we must handle the location change properly.



 Comments   
Comment by Christopher Zimmermann [ 29/Nov/12 ]

This sounds important.
If you feel it should not be in s010 sprint, or want to assign to someone else, let's discuss.

Comment by Espen Jervidalo [ 10/Jan/13 ]

fixed on vaadin7 branch

Generated at Mon Feb 12 08:37:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.