How do I avoid this issue?

[Joel Cairney]

I'm working on a large GWT application, and on chrome for android we're running into these issues:

https://code.google.com/p/chromium/issues/detail?id=258044

The HTML and CSS patterns that create this issue are commonly found in GWT widgets, or are easily created by combining widgets.  I haven't seen any movement on this issue on the Chromium list, and don't have confidence that their rendering will get fixed any time soon.  Can anyone recommend a way to work around these issues?

[Michael Prentice]

I'm not sure how to avoid it but I've starred it. Sounds like a pretty nasty issue.

[Joel Cairney]

DataGrids have absolutely positioned hidden divs with overflow: scroll, which can cause issue #2 from the linked bug above.  And since they may be absolutely positioned in a layout, if issue #1 hasn't occurred elsewhere on the page, DataGrids may create issue #1 instead.

Also, ScrollPanel, which our developers rely on heavily is a good example of a div that will get absolutely positioned and have overflow: auto, and depending on content probably have in-flow elements that will require scrolling, and will contain at least one absolutely position div, since many GWT widgets have a hidden one.  This will cause issue #1.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/VBj2kRCrlRs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.