Summary: | Google Maps "Earth" mode stops getting new data until safari restarts | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Ryan Sturgell <rsturgell> | ||||
Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED INVALID | ||||||
Severity: | Normal | CC: | ap, bburg, ddkilzer, ggaren, heppe, mitz, sam, webkit-bug-importer, zalan | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Safari 9 | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.11 | ||||||
Attachments: |
|
Description
Ryan Sturgell
2016-02-18 15:42:56 PST
If opening a new window doesn't fix the bug, it can't be a JavaScript bug. Most likely, this bug has to do with networking and the network process -- or perhaps storage and the storage process -- which are the only things that survive across new windows. Earth mode is now disabled for safari users. To repro you'll need to: 1. set chrome as the useragent 2. force webgl mode: https://google.com/maps?force=webgl Please let me know if you have any trouble reproducing, of if there are any testing I can do that would be helpful to track this down. While in the state of not updating the map tiles with new data 1. while panning around in the original tab, webinspector still shows network activity (the pattern of the requests indicate tile data) 2. opening a new tab and going to maps shows black page and while I can trigger network traffic by initiating map searches, panning/zooming shows no activity at all. However it seems that most of the XHR requests are either pending or come back with some error code. Terminating the network process fixes the problem. Does this issue still manifest on macOS Sierra? I upgraded my corp laptop to sierra, and after about 5 min of playing with it I wasn't able to reproduce. If we want to narrow the scope of for whom we turn off Earth view, should we select based on OS, or is Safari version sufficient? If the former, is that even possible from within javascript? The fix was in a system library below WebKit (so marking this WebKit bug as INVALID), and shipped with macOS Sierra and iOS 10. The OS version is part of user agent string, so it can be checked from JavaScript (navigator.appVersion), or even from HTTP request header. Disabling HTTP/2 server side may be a workaround for older OS versions. Falling back to 2d is fine for the gradually dwindling base of Pre-Sierra safari users. We'll roll out a fix to re-enable for Sierra+ users that should hit in the mid-January time frame. Thanks for the info! |