JDK-8116399 : Yandex Maps are broken after sync with WebKit trunk
  • Type: Bug
  • Component: javafx
  • Sub-Component: web
  • Affected Version: 8
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-08-01
  • Updated: 2015-06-17
  • Resolved: 2013-08-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Relates :  
Description
Yandex Maps (maps.yandex.ru) are broken again, presumably by the recent sync with WebKit trunk, see RT-31450.

The problems are:
    - The Zoom In/Zoom Out ruler does not appear
    - Mouse dragging does not scroll the map
Comments
Verified on 8.0b104
27-08-2013

The fix has been pushed as http://jfxsrc.us.oracle.com/javafx/8.0/scrum/graphics/rt/rev/91a8ecbea96e
06-08-2013

There are two problems here, both introduced by the recent sync with WebKit trunk. First, the sync added the ENABLE_REQUEST_ANIMATION_FRAME build feature but did not provide a meaningful implementation for ChromeClient::scheduleAnimation(). That caused certain applications like Yandex Map to start behaving as if requestAnimationFrame was supported while it really isn't, producing unexpected results. The second problem is, the WebCore::StorageAreaJava class implementation has got out of sync with WebCore::StorageAreaImpl, which caused certain scripts to start failing with an unexpected security exception when trying to assess window.sessionStorage. Here is the fix, up for code review: http://sthinfra10.se.oracle.com:8060/cru/CR-FX8GFX-210 Webrev: http://javaweb.us.oracle.com/jcg/fx-webrevs/RT-32039/1 Note that I am also removing the ENABLE_SMOOTH_SCROLLING feature. That is because it requires ENABLE_REQUEST_ANIMATION_FRAME which needs to be disabled for now.
02-08-2013