exploretock.com - Map is not displayed
Categories
(Web Compatibility :: Site Reports, defect, P1)
Tracking
(Webcompat Priority:P1, Webcompat Score:1, firefox132 wontfix, firefox133 wontfix, firefox138 wontfix, firefox144 fixed)
People
(Reporter: ipop, Assigned: twisniewski)
References
()
Details
(Keywords: webcompat:needs-diagnosis, webcompat:site-report, webcompat:sitepatch-applied, Whiteboard: [webcompat-source:product])
User Story
platform:windows,mac,linux,android impact:workflow-broken configuration:general affects:all branch:release user-impact-score:800 diagnosis-team:graphics
Attachments
(3 files)
Environment:
Operating system: Windows 11/10
Firefox version: Firefox 131.0.3 (release)/133
Preconditions:
- Clean profile
Steps to reproduce:
- Navigate to: https://www.exploretock.com/city/san-antonio/search?city=San%20Antonio&date=2024-10-22&latlng=29.4241219%2C-98.4936282&size=2&time=18%3A00&type=DINE_IN_EXPERIENCES
- Observe the behavior
Expected Behavior:
The map is displayed properly.
Actual Behavior:
The map is not displayed.
Notes:
- Reproducible on the latest Firefox Release and Nightly
- Reproducible regardless of the ETP setting
- Works as expected using Chrome
Created from webcompat-user-report:4b89a0af-313f-416b-a089-155d2433fbac
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 1•1 year ago
|
||
The issue is still reproducible on the latest Nightly.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
https://github.com/webcompat/web-bugs/issues/100874#issuecomment-1611839988 has some diagnosis
Comment 3•1 year ago
|
||
In Chrome webgl.js throws the following exception:
SecurityError: Access to the script at 'blob:https://www.exploretock.com/aead7bfa-49a4-4516-9ddc-4f06047b3314' is denied by the document's Content Security Policy.
from:
, WR = function(a, b) {
return new Worker(_.Uf(a),b)
}
Updated•1 year ago
|
Comment 4•11 months ago
|
||
The issue is still reproducible
Tested with:
Browser / Version: Firefox Nightly 139.0a1 (2025-04-21) (64-bit)
Operating System: Windows 10 PRO x64
Comment 5•11 months ago
•
|
||
Bug 1471805 was closed as won't fix. So we'll probably need to site-patch this while we wait for other browsers.
Updated•11 months ago
|
| Assignee | ||
Updated•9 months ago
|
| Assignee | ||
Comment 6•9 months ago
|
||
Updated•9 months ago
|
| Assignee | ||
Updated•9 months ago
|
Updated•9 months ago
|
Comment 9•7 months ago
|
||
I believe Chrome has shipped compatible behaviour with us on re: bug 1471805
This page works with the intervention disabled.
And then the intervention seems to be causing problems: bug 1984463
Tom, can we remove the intervention and uplift?
| Assignee | ||
Comment 11•7 months ago
|
||
| Assignee | ||
Updated•7 months ago
|
Comment 12•7 months ago
|
||
Comment 13•7 months ago
|
||
| bugherder | ||
Updated•7 months ago
|
Description
•