Can't open roblox
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox64 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | --- | verified |
People
(Reporter: aydanoliver, Assigned: baku)
References
(Regressed 1 open bug)
Details
(Keywords: parity-chrome, regression, site-compat)
Attachments
(2 files)
1.09 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
10.32 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
Comment 1•6 years ago
|
||
Reporter | ||
Comment 2•6 years ago
|
||
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Andrei, can your team look for a regression range? Thanks!
Comment 7•6 years ago
|
||
regression-window |
I have managed to reproduce this issue using Firefox 66.0a1 (BuildId:20190122215349) on Windows 10 64bit and macOS 10.13.6.
This seems to be a regression:
Last good revision: 2ee2f297c4106e017231ed67fba4034d766c942b
First bad revision: c4bf214bd2e65e460fcd24a6483635c1d5cb4771
It seems that, on good builds, a prompt was displayed giving the user an option to launch the Roblox application (on affected builds, the prompt is no longer displayed and the game cannot be launched).
The following error pops inside the browser console:
9ef8bbfc2eab421bb393f587d2fff95d.js.gzip:127:210
XML Parsing Error: no root element found
Location: https://assetgame.roblox.com/game/report-event?name=GameLaunchAttempt_Win32
Line Number 1, Column 1: report-event:1:1
XML Parsing Error: no root element found
Location: https://assetgame.roblox.com/game/report-event?name=GameLaunchAttempt_Win32_Protocol
Line Number 1, Column 1: report-event:1:1
TypeError: docShell.failedChannel is null NetErrorChild.jsm:728:13
Hi Andrea! Can you please have a look into this? Thanks!
Assignee | ||
Comment 8•6 years ago
|
||
Can you check if bug 1517368 fixes this issue?
Comment 9•6 years ago
|
||
Unfortunately, Bug 1517368 doesn't seem to fix this issue.
Assignee | ||
Comment 10•6 years ago
|
||
This patch does 2 things in 1 line:
- It doesn't show an error message when the iframe is blocked.
- Because of this, it keeps the same URL loaded in the iframe.
I don't have a nice way to write a test for it.
Assignee | ||
Comment 11•6 years ago
|
||
As discussed on IRC, this patch introduces the concept of 'timing' token for external protocol iframe. At the moment, this token is used just for iframe, and I don't want to generalize it for a bigger scope.
The idea is this:
-
if external protocol iframes are loaded with user-interaction, PopupBlocker uses the user-interaction token as before.
-
if they are loaded without user interaction, if the window is active, PopupBlocker tries to use the timing token: only 1 external protocol iframe is allowed any 20 seconds. (20 secs is by pref).
I expose the timing to chromeUtils for the testing.
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/eac3071c276b
https://hg.mozilla.org/mozilla-central/rev/910e176da1f9
Updated•6 years ago
|
Comment 16•6 years ago
|
||
This issue is verified fixed using Firefox 66.0a1 (BuildId:20190127213438) on Windows 10 64bit and macOS 10.11.6
Updated•6 years ago
|
Updated•6 years ago
|
Description
•