Bug 177602
Summary: | WebGL content is black after switching tabs | ||
---|---|---|---|
Product: | WebKit | Reporter: | Kirill S. Dmitrenko <kdmitrenko> |
Component: | WebGL | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | ap, dino, jonlee, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 10 | ||
Hardware: | Mac | ||
OS: | macOS 10.12 |
Kirill S. Dmitrenko
1. Open https://yandex.com/maps/213/moscow/?ncrnd=3459&ll=37.583335%2C55.733222&z=16&l=stv%2Csta&panorama%5Bpoint%5D=37.588440%2C55.733808&panorama%5Bdirection%5D=171.429911%2C-4.006784&panorama%5Bspan%5D=120.000000%2C75.351069
2. Drag panoramic image
3. Swtich tab
4. Return to the tab with Yandex.Maps
5. Player is black
That's a regression that was introduced in Safari 11 (same problem in TP). I wasn't able to isolate smaller test case:( Is there a way to debug this with internal WebKit tools?
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
I cannot reproduce this with macOS High Sierra on a 15" Mid 2015 MacBook Pro.
What hardware and OS are you using? Can you try other configurations to further isolate the problem?
Jon Lee
I could reproduce on iMac. As soon as I drag again the panorama returns.
Kirill S. Dmitrenko
(In reply to Alexey Proskuryakov from comment #1)
> I cannot reproduce this with macOS High Sierra on a 15" Mid 2015 MacBook Pro.
>
> What hardware and OS are you using? Can you try other configurations to
> further isolate the problem?
macOS 10.12.6 (16G29), MacBook Pro (Retina, 13-inch, Late 2013)
macOS 10.12.6 (16G29), MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports)
Wasn't able to repro on 10.12.6 (16G29) on MacBook Air (13-inch, Mid 2011)
Radar WebKit Bug Importer
<rdar://problem/34740792>
Kirill S. Dmitrenko
Any news?
Jon Lee
Not yet, but it's in our queue.
Dean Jackson
I can no longer reproduce this on a MacBook Pro or Mac Pro running the seed of 10.13.4, using Safari Technology Preview 48.
Kirill, can you try again with an updated configuration?
Kirill S. Dmitrenko
We can't reproduce the problem on available configurations too (Safari 11.0.3 on 10.11.6, 10.12.6 and 10.13.3). And there're no more user complaints about it to our support.