[MGNLUI-3329] Vaadin requests are not sent in time from Page Editor and during navigation with 1-3 keys (since Vaadin 7.3 update). Created: 22/Jan/15 Updated: 06/Aug/15 Resolved: 16/Feb/15 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | page editor |
| Affects Version/s: | 5.2.11, 5.3.7, 5.4 |
| Fix Version/s: | 5.2.12, 5.3.8 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pageeditor, support, vaadin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| 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 |
|
Issue: sometimes the user action (like click or key press) is not propagated to server unless browser event occurs (like mouse move/hover). Steps to reproduce in Page Editor:
Similar case in ShellApp:
The 5.3 installations are not affected which puts an update to Vaadin 7.3.4 (since 5.4) into suspicion. |
| Comments |
| Comment by Mikaël Geljić [ 13/Feb/15 ] |
|
also affects IE10/11 on current Vaadin version (7.1.7) |
| Comment by Aleksandr Pchelintcev [ 16/Feb/15 ] |
|
In short - the problem was with the GWT code we expose to the JS code (e.g. JQuery callbacks, CKEditor listeners, Pages Editor iframe interactions). Triggered from outside of GWT those methods wouldn't cause GWT's scheduler to finalize the user event processing and Vaadin's RPC queue wouldn't be flushed. It used to work because coincidentally there used to be a timer that was triggering the queue flushing on a regular basis (apparently not for the case of IE 10/11). Wrapping exposed GWT methods with GWT's $entry(function) function cures the issue. |
| Comment by Richard Unger [ 20/Mar/15 ] |
|
What's the status here? There don't seem to be any fix versions noted? This is affecting us in 5.3.7... |
| Comment by Mikaël Geljić [ 20/Mar/15 ] |
|
Hi Richard, For the story, this is caused partially because we're "stuck" with Vaadin 7.1 series on Magnolia 5.3, and presumably because of some legacy code from the Vaadin 6 era. The workaround for now is to use IE9 Compatibility mode — which Anyway, this ticket here fixes one of these legacy problems (and is indeed targeted at 5.4), while Cheers, |
| Comment by Richard Unger [ 20/Mar/15 ] |
|
Hi Mika, Thanks for the feedback. Yes indeed, the issue occurs only in IE10 & IE11 (also in IE9 mode) but the issue we are encountering isn't to do with the 1-3 keys, it is simply that the action bar does not update as you select different components/areas in the editor. Once you move the mouse onto the action bar it updates. I opened a support ticket for it. Thanks! |