Closed
Bug 554451
Opened 16 years ago
Closed 9 years ago
plugin crash notification "no report available" is probably meaningless to most
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: asa, Assigned: timeless)
Details
Attachments
(2 files)
|
9.60 KB,
image/png
|
Details | |
|
1.06 KB,
patch
|
Dolske
:
review-
|
Details | Diff | Splinter Review |
The plugin crash notification has been telling me "no report available" but I have no context for that and have no idea what it's trying to say to me. I suspect that "regular folks" will have even less an idea what that's saying. We either need to explain better what it is or remove it.
tested on latest nightly build on windows 7.
Comment 2•15 years ago
|
||
I am now getting crashes more frequently on Mac that have this issue, and Asa filed Bug 624809 for the Windows issue.
Can someone explain to me why we get this notification with Plugin crashes? And would the underlying reason be different on different operating systems? adding dolske since juanb said he might have some insight.
Comment 4•14 years ago
|
||
Comment on attachment 507034 [details] [diff] [review]
proposal
Review of attachment 507034 [details] [diff] [review]:
-----------------------------------------------------------------
I've bounced back and forth on this over time, but I think I've now settled in on agreeing that we should just remove the string.
But let's be complete. In addition to the CSS parts in this patch, please also remove:
* the relevant <div> from pluginProblem.xml
* the report.unavailable entity from plugins.dtd
The reference to |status = "noReport"| in browser.js can stay.
Attachment #507034 -
Flags: review?(dolske) → review-
Comment 5•9 years ago
|
||
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•