"Include the address of the page I was on" is not ticked by default in Crash Reporter
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | verified |
| firefox129 | --- | wontfix |
| firefox130 | --- | wontfix |
| firefox131 | --- | verified |
People
(Reporter: btot, Assigned: afranchuk)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr128+
|
Details | Review |
Found in
- Beta 130.0b1
Affected versions
- Nightly 131.0a1
- RC 129.0
Tested platforms
- Affected platforms: macOS 14, macOS 12 ARM, Windows 11, Ubuntu 24
- Unaffected platforms: -
Steps to reproduce
- Launch Firefox, with a new profile.
- Open one random page and then crash the browser with "about:crashparent".
- Pay attention to the two checkboxes inside the crash reporter dialog
Expected result
- Both check boxes should be ticked by default.
Actual result
- The "Include the address of the page I was on." checkbox is NOT ticked by default.
Regression range
- Look for it asap
| Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=49f6b516c694f8b513f25f9b215da350f43d13ad&tochange=538aa6838630426342580bd8ea1330e0fcf3d56c
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1759175
:afranchuk, since you are the author of the regressor, bug 1759175, could you take a look?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 3•2 years ago
|
||
This was an intentional change to be more conservative with personal information by default, however I'm okay with changing it back. :gsvelto thoughts?
Comment 4•2 years ago
|
||
Did we put the rationale for this decision in some bug?
| Assignee | ||
Comment 5•2 years ago
|
||
No. I originally did it because I thought that was the default (misinterpreting some code I read). A little later I realized my mistake but thought it might be better to stick with that. We can definitely change it back.
Comment 6•2 years ago
|
||
OK, let's check it by default. While digging around I found bug 1781087 which I had filed precisely to ensure that the default is to have it checked by default everywhere if the user never interacted with the field.
Updated•2 years ago
|
| Assignee | ||
Comment 7•2 years ago
|
||
This default is used when the crash reporter has never been launched
before. Notably, this is currently a user-global setting (as opposed to
per-profile), so the defaults will typically only be used when someone
hasn't ever had Firefox installed on their system.
Updated•2 years ago
|
Comment 9•2 years ago
|
||
| bugherder | ||
Comment 10•2 years ago
|
||
The patch landed in nightly and beta is affected.
:afranchuk, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox130towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
:afranchuk do you want to add an esr128 uplift request?
| Assignee | ||
Comment 12•2 years ago
|
||
This default is used when the crash reporter has never been launched
before. Notably, this is currently a user-global setting (as opposed to
per-profile), so the defaults will typically only be used when someone
hasn't ever had Firefox installed on their system.
Original Revision: https://phabricator.services.mozilla.com/D218887
Updated•2 years ago
|
Comment 13•2 years ago
|
||
esr128 Uplift Approval Request
- User impact if declined: None
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: N/A
- Risk associated with taking this patch: Very minimal
- Explanation of risk level: Merely changes a default setting in the crash reporter client.
- String changes made/needed: None
- Is Android affected?: no
| Assignee | ||
Comment 14•2 years ago
|
||
That's probably a good idea, just to encourage more information that may help to reproduce/diagnose/debug issues.
| Assignee | ||
Updated•2 years ago
|
Updated•1 year ago
|
Comment 15•1 year ago
|
||
| uplift | ||
Updated•1 year ago
|
| Reporter | ||
Comment 16•1 year ago
|
||
Verified as fixed on latest Nightly 131.0a1 and ESR 128.2.0esr build.
| Reporter | ||
Updated•1 year ago
|
Description
•