search

OpenESignForms / openesignforms

Open eSignForms is the first open source SaaS web contracting platform
https://open.esignforms.com
107 stars 50 forks source link

HTML Editor scrolls on first actions involving buttons, sometimes causing position errors #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Bring up a Form that includes an HTML editor.
2. Hit ENTER to insert a line, then click INSERT TABLE button on the editor.
3. Generally, if you then click OK, the table will be inserted at the top or 
bottom of the editor, not where you were positioned.

What is the expected output? What do you see instead?
The editor should not scroll and lose its position.

This not only happens when inserting a new table, but also on first load of the 
editor, if you highlight some text and then click a button to change the style, 
for example, it will scroll away and the style won't be applied.

Oddly, after this first time scroll bug, it does not occur again, during the 
editing session.

Original issue reported on code.google.com by yoz...@gmail.com on 24 May 2011 at 2:25

GoogleCodeExporter commented 9 years ago 
NOTE: Yozons is working with Vaadin for a possible solution. It does not appear 
to be related to the CKEditor component. It seems to occur when the CKEditor 
component is embedded in a Vaadin Form with setImmediate(true), or it not, when 
some other button is first pressed causing the state of the editor to be 
transmitted, which then causes the editor to scroll.

Current work around is either to do this once knowing it will fail, or with 
some instances, we've turned off setImmediate(false).  The first-time scrolling 
bug is still there, but it occurs when you click outside of the editor, so it 
doesn't "mess up" anything you were doing, though it does lose its position in 
the editor, so you have to scroll back to where you were before.

Original comment by yoz...@gmail.com on 24 May 2011 at 2:28

GoogleCodeExporter commented 9 years ago 
Here's the link to the Vaadin forum discussion on this, which is still rather 
mysterious:

http://vaadin.com/forum/-/message_boards/view_message/461390#_19_message_461390

Original comment by yoz...@gmail.com on 24 May 2011 at 2:29

GoogleCodeExporter commented 9 years ago 
Created ticket with Vaadin:

http://dev.vaadin.com/ticket/7121

Original comment by yoz...@gmail.com on 3 Jun 2011 at 4:34

GoogleCodeExporter commented 9 years ago 
Dropped priority since we're not really seeing it much now since turning off 
setImmediate, but that's more a workaround than a fix since if immediate is on, 
the problem still exists. We believe this is a Vaadin issue more than something 
we can resolve.

Original comment by yoz...@gmail.com on 16 Aug 2011 at 11:28

GoogleCodeExporter commented 9 years ago 
We are closing this because we don't see it as an issue anymore. If we find it 
again, we can re-open it or create a new ticket.

Original comment by yoz...@gmail.com on 12 Apr 2012 at 10:52