Empty alerts when browser.xul.error_pages.enabled=false
Categories
(Firefox :: Security, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: mavit+bugzilla.mozilla.org, Assigned: stensonj)
References
()
Details
(Keywords: good-first-bug)
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
- Went to about:config and set
browser.xul.error_pages.enabledtofalse. - Browsed to https://expired.badssl.com/
Actual results:
A window appeared titled "Alert", containing ⚠ and an OK button, but nothing else.
Expected results:
I should have received a message along the lines of "Firefox detected an issue and did not continue to expired.badssl.com. The web site is either misconfigured or your computer clock is set to the wrong time".
It's been a long time since browser.xul.error_pages.enabled=true was made the default. If changing it no-longer works reliably, perhaps it's time for this option to be removed?
Comment 1•6 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
20191030050308
gfx.webrender.force-disabled set to true doesn't help, so this isn't bug 1573710.
Comment 2•6 years ago
|
||
It's been a long time since browser.xul.error_pages.enabled=true was made the default. If changing it no-longer works reliably, perhaps it's time for this option to be removed?
Yeah, I'd say it's to time to say goodbye. Dan, Mike, does one of you have any old time anecdotes on what this is why we might still need it? :)
Comment 3•6 years ago
|
||
I don't see any reason to keep it. they've been pages for a very long time.
Comment 5•6 years ago
|
||
Thanks!
| Assignee | ||
Comment 6•6 years ago
|
||
Hi there, I would like to work on this. Could you give me some pointers as to what to do to solve it? Thanks
(Requested info from reporter as mentor is away till Dec 3rd)
| Reporter | ||
Comment 7•6 years ago
|
||
(In reply to Jacob Stenson from comment #6)
Hi there, I would like to work on this. Could you give me some pointers as to what to do to solve it? Thanks
(Requested info from reporter as mentor is away till Dec 3rd)
I'm not a Firefox developer, so can only offer very general advice. Start at https://dxr.mozilla.org/mozilla-central/search?q=regexp%3Abrowser.xul.error_pages.enabled&redirect=false. Remove any mention of the setting from the code, and modify anything that tries to use the setting so that it acts as if the setting was set to true. If the tests pass then you probably did it correctly. Good luck!
| Assignee | ||
Comment 8•6 years ago
|
||
Hi, I am currently working on this bug but running into an issue where when I edit the code in the files found at the link you specified, nothing in the built browser changes. I can even delete entire files and the browser still functions as normal. I understand the reporter of this bug is not a firefox dev so does anyone else have any idea what is going on? Is there something I must do differently to fix this issue compared to other bugs? Thanks
Comment 9•6 years ago
|
||
Nothing in the built version of Firefox should change. You're removing code that isn't used anymore.
| Assignee | ||
Comment 10•6 years ago
|
||
I know. I was removing code and testing but nothing was changing. It was as if I had not removed any code at all
| Assignee | ||
Comment 11•6 years ago
|
||
Am I not also removing the "browser.xul.error_pages.enabled" setting from the about:config page?I have removed all mentions of the code from the files listed in this link: https://dxr.mozilla.org/mozilla-central/search?q=regexp%3Abrowser.xul.error_pages.enabled&redirect=false . but the setting still shows up in about:config and the browser still acts in the same way with regards to the setting being set to true or false.
Comment 12•6 years ago
|
||
This code is what puts it in about:config
https://searchfox.org/mozilla-central/source/modules/libpref/init/StaticPrefList.yaml#998
| Assignee | ||
Comment 13•6 years ago
|
||
(In reply to Mike Kaply [:mkaply] from comment #12)
This code is what puts it in about:config
https://searchfox.org/mozilla-central/source/modules/libpref/init/StaticPrefList.yaml#998
I have removed said code and nothing changes in about:config.
Comment 14•6 years ago
|
||
Is it bold in about:config? That means it was set by you, so it will stick around.
| Assignee | ||
Comment 15•6 years ago
|
||
(In reply to Mike Kaply [:mkaply] from comment #14)
Is it bold in about:config? That means it was set by you, so it will stick around.
No it isnt bold. Could you try removing the code in StaticPrefList.yaml and see if you run into the same issue?
Comment 16•6 years ago
|
||
Are you doing an artifact build or a full Firefox build?
Changes to the YAML for preferences requires a full build (since there are cpp/h file changes).
Can you post your patch?
| Assignee | ||
Comment 17•6 years ago
|
||
Im running "./mach run" in my firefox folder which opens up Nightly, are you saying I have to run "./mach build" to see any changes in about:config? I can post my patch with code I believe will work, although I have not tested it yet.
Comment 18•6 years ago
|
||
Yes, when you make code changes, you need to do ./mach build to build those changes.
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions
| Assignee | ||
Comment 19•6 years ago
|
||
I have not been using ./mach build for previous bugs I have been working on. Is this different due to the fact I am working on cpp/h files? Just to confirm
Comment 20•6 years ago
|
||
Yes, although I'm surprise you didn't need to build Firefox at all for your other bugs.
| Assignee | ||
Comment 21•6 years ago
|
||
I built it originally and then started working on bugs, using ./mach run to test the updated code. From now on I'll use ./mach build to test code for this bug!
| Assignee | ||
Comment 22•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 24•5 years ago
|
||
It seems like we're blocked on info from Thunderbird devs here and Mike wanted to reach out, has there been any progress?
Comment 25•5 years ago
|
||
I reached out, but they didn't have an answer (too long ago). I think we should assume they need it and just remove stuff for Firefox only.
Comment 28•5 years ago
|
||
No, I'll pick up and remove the changes that break thunderbird.
Updated•5 years ago
|
Comment 29•5 years ago
|
||
This person on reddit had this error pages is disabled and it totally broke their browsing experience. We should remove it.
Comment 30•5 years ago
|
||
Argh. This got reviewed and I didn't get notified. Sorry, I'll get it checked in.
Comment 31•5 years ago
|
||
Comment 32•5 years ago
|
||
| bugherder | ||
Description
•