Closed GoogleCodeExporter closed 9 years ago
If you don't see this effect try to further reduce the vertical size. I always
get this error if I reduced enough to only see half of the middle gray
rectangle.
thanks
Original comment by ricard.n...@gmail.com
on 16 Jul 2010 at 10:06
I have the same issue in IE.
I think I have a workaround though. If you create another scrollable panel so
that the page body does not move, the behaviour is correct. The downside is
that everything happens in the secondary panel and a double scrollbar is
displayed
Original comment by WKenigsb...@gmail.com
on 13 Oct 2010 at 4:36
Confirmed that this is due GWT's implementation of scrollIntoView(), which,
although better than the built-in scrollIntoView() browser method, is still
defective is some ways.
Please vote for this GWT issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5529
Also, please attach the simplest possible test case which reproduces the issue,
ideally with a few lines of code to construct the UI, followed up a (delayed?)
call to scrollIntoView() so that the effect is visible.
Original comment by fredsa@google.com
on 3 Nov 2010 at 12:49
Also, I should mention this workaround to avoid the problematic call:
dragController.setBehaviorScrollIntoView(false);
Original comment by fredsa@google.com
on 3 Nov 2010 at 12:55
I tried to open the above link
http://allen-sauer.com/com.allen_sauer.gwt.dnd.demo.DragDropDemo/DragDropDemo.ht
ml#AbsolutePositionExample in IE9 beta browser (version: 9.0.7930.16406 64-bit
edition) under Windows 7 Professional, but I've got an exception:
Uncaught exception: com.google.gwt.core.client.JavaScriptException:
(undefined): DOM Exception: INVALID_CHARACTER_ERR (5)
Print screen could be found in the attached PNG file. Should I for this
issue/exception also open a bug report in GWT domain?
Original comment by andrejna...@yahoo.com
on 3 Nov 2010 at 8:52
Attachments:
I'm seeing a different error in IE9, which appears to be this issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5058
Original comment by fredsa@google.com
on 3 Nov 2010 at 10:56
Specifying a standards mode DOCTYPE on your main HTML page may help with this
one
Original comment by fredsa
on 31 Jan 2012 at 6:19
Original issue reported on code.google.com by
ricard.n...@gmail.com
on 16 Jul 2010 at 9:59