JDK-8124576 : Some websites render garbage when scrollbar is used on Linux
  • Type: Bug
  • Component: javafx
  • Sub-Component: web
  • Affected Version: 8
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-04-29
  • Updated: 2015-06-17
  • Resolved: 2013-08-06
Related Reports
Duplicate :  
JDK-8124034 - use the WebView or WebEngine that open the big data of webpage,it's very slow and screenshots is very bad
Relates :  
JDK-8126811 - Google Maps in WebView causes exception on Ubuntu
Relates :  
JDK-8116399 - Yandex Maps are broken after sync with WebKit trunk
Relates :  
JDK-8124133 - salesforce.com is rendered poorly in SW mode
Relates :  
JDK-8101977 - Support touch events in WebView
Relates :  
JDK-8123698 - Some websites are rendered poorly
Description
Some websites render garbage when scrollbar is used on Linux.
Among them are:
http://capitalone.com

Check attached screenshot for capitalone.com as an example.

This can be seen in both hardware mode (as reported by Evergreen) and software (default fallback) mode.
Comments
Please, set value for "Fix Version/s" field.
30-01-2014
This issue has been fixed by RT-32039.
06-08-2013
This is the same issue as in RT-32039. As far as I can see all problems disappear if I apply the fix from RT-32039.
02-08-2013
This might be related to RT-31536 - many of affected websites are also affected by that bug.
22-07-2013
Affected tests: sites/craiglist.org.html sites/craigslist.com.html sites/go.com.html sites/salesforce.com.html sites/windows.com.html sites/yelp.com.html
22-07-2013
Previously affected tests: sites/capitalone.com.html sites/craiglist.org.html sites/craigslist.com.html sites/go.com.html sites/nytimes.com.html sites/salesforce.com.html sites/windows.com.html sites/yelp.com.html
22-07-2013
I'm afraid I'll have to reopen this issue. As for Lombard b99, the problem still manifests itself (on Ubuntu 12.04, 32bit, SW mode at least). Not all the sites which were reported initially are affected, but it looks pretty much the same for the rest.
22-07-2013
The fix has been pushed as http://jfxsrc.us.oracle.com/javafx/8.0/scrum/graphics/rt/rev/285f987b64ca
17-05-2013
So for the AC case we even save one JNI upcall. Cool ;)
15-05-2013
Here is the fix. Webrev: http://javaweb.us.oracle.com/jcg/fx-webrevs/RT-30080/3 The idea is to call the root layer's setNeedsDisplayInRect() method in response to ChromeClient::scroll() request when accelerated compositing is in effect, as other ports do. Testing: http://capitalone.com http://craiglist.org http://craigslist.com http://go.com http://nytimes.com http://salesforce.com http://windows.com http://yelp.com http://www.webkit.org/blog-files/leaves http://javaweb.sfbay.sun.com/~epavlova/Performance/JavaFX2/mexsantos http://neography.com/experiment/circles/solarsystem http://meyerweb.com/eric/css/edge/complexspiral/demo.html http://davidwalsh.name/demo/css-fixed-position.php http://demo.tutorialzine.com/2010/06/microtut-how-css-position-works/demo.html
14-05-2013
This is in fact a regression from RT-RT-22913, masked by RT-29123.
14-05-2013
It turns out many of those issues are regressions from RT-29123. Once the regression is fixed, we'll revisit the touch events issue.
08-05-2013
In addition to removing touch events from build files, this webrev also cleans up Java code. Overall this fix is a partial revert of RT-21052. http://javaweb.us.oracle.com/jcg/fx-webrevs/RT-30080/2
07-05-2013
This is the famous touch event problem again. See RT-22914 for details. The problem with all those sites is: they detect presence of 'ontouchstart' and similar touch-related attributes, and switch to touch interface, ignoring mouse events completely. We enable touch events at build time, so WebView has those attributes defined even if the hardware it runs on is not touch capable. So both sides are guilty: sites could arguably do a better job at handling both types of events, and we're lying about being able to send touch events when we are not. Ideally we'd check for touch-enabled hardware at runtime, and turn touch event support on or off respectively. Unfortunately there's no simple way to do that with Webkit. We could probably hack into the JS machine and undefine 'ontouchstart' and similar attributes, but this is going to be an unreliable hack. So I suggest turning touch event support back off in WebView. We may want to investigate the JS machine hacking option later if people complain. Webrev: http://javaweb.us.oracle.com/jcg/fx-webrevs/RT-30080/1
07-05-2013