Open
Bug 1828113
Opened 1 year ago
Updated 2 months ago
about:neterror - No strings exist for error: corruptedContentErrorv2
Categories
(Core :: Networking, defect, P2)
Core
Networking
Tracking
()
NEW
People
(Reporter: tschuster, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, Whiteboard: [necko-triaged][necko-priority-next])
I noticed this in on a non-public test case:
No strings exist for error: corruptedContentErrorv2 aboutNetError.mjs:383:13
initPage chrome://global/content/aboutNetError.mjs:383
<anonymous> chrome://global/content/aboutNetError.mjs:1448
Probably this line needs to be updated.
Comment 1•1 year ago
|
||
The severity field is not set for this bug.
:serg, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(sgalich)
Updated•1 year ago
|
Severity: -- → S3
Flags: needinfo?(sgalich)
Priority: -- → P3
Updated•7 months ago
|
Blocks: necko-error
Comment 2•2 months ago
|
||
Moving to Necko component
Severity: S3 → --
Component: Security → Networking
Priority: P3 → --
Product: Firefox → Core
Updated•2 months ago
|
Severity: -- → S3
Priority: -- → P3
Whiteboard: [necko-triaged]
This line should be changed to "corruptedContentErrorv2-title"
"corruptedContentError-title",
Points: --- → 1
Keywords: good-first-bug
Priority: P3 → P2
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-next]
You need to log in
before you can comment on or make changes to this bug.
Description
•