RFP breaks Sync login
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Tracking
(Not tracked)
People
(Reporter: ti8bpxk2y, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
326.66 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
- Turn on RFP
- Try to login at https://accounts.firefox.com
Actual results:
An error page is displayed, I attached a screenshot.
Expanding the error shows the following:
n@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:13512
diff@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:13673
getLoad@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:16036
getAllData@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:24200
getFilteredData@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:25542
flush@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:23181
logEvent@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:26314
logView@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:27090
logView@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:1:37891
showView/</<@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/app.bundle.en_US.js:9:110916
invoke@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:84:6401
run@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:84:1809
R/<@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:99:2761
invokeTask@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:84:7019
runTask@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:84:2424
m@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:84:9056
invokeTask@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:84:8124
p@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:115:743
d@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:115:1058
_@https://accounts-static.cdn.mozilla.net/bundle-ca5431743db94d007649461e21e3cb2d0c7f70ff/appDependencies.bundle.js:115:1357
In the console instead I see:
TypeError: can't access property "performance", this is undefined
Expected results:
The login screen is displayed as usual.
Comment 2•1 year ago
|
||
So 108 wasn't affected? Can you run a moz-regression?
Went as back as 96.0.2 with moz-regression and it showed the same error, it must be a server side change right?
Comment 4•1 year ago
|
||
This looks like an error where we are disabling performance APIs under RFP; and the website doesn't check that the object exists.
I intend to fix this soon by undoing that restriction soon.
Thanks Tom, that should also help with some of the reports in https://bugzilla.mozilla.org/show_bug.cgi?id=1621729. Could you mark that ticket as related as well, so that we remember to double-check once the fix will land?
Updated•1 year ago
|
Comment 8•1 year ago
|
||
The following field has been copied from a duplicate bug:
Field | Value | Source |
---|---|---|
Status | NEW | bug 1811255 |
For more information, please visit auto_nag documentation.
Comment 9•1 year ago
|
||
This should have been fixed by bug 1811567.
Reporter | ||
Comment 10•1 year ago
|
||
Tested with Nightly 111.0a1. Thanks!
Description
•