Closed Bug 243387 Opened 21 years ago Closed 21 years ago

about:plugins broken by download size reduction changes

Categories

(Firefox :: General, defect, P2)

defect

Tracking

()

VERIFIED FIXED
Firefox0.9

People

(Reporter: bugs, Assigned: bugs)

Details

(Keywords: regression, Whiteboard: fixed-aviary1.0)

Attachments

(2 files, 2 obsolete files)

my pruning of the communicator package removed the about:plugins page. Need to add it back.
Status: NEW → ASSIGNED
Flags: blocking0.9+
Priority: -- → P2
Target Milestone: --- → Firefox0.9
Attached patch patch (obsolete) — Splinter Review
We need plugins.html, plugins.properties and region.properties in communicator-region; in order to register the latter, we need the appropriate contents.rdf as well. The first change is just whitespace.
Assignee: bugs → steffen.wilberg
Attachment #148351 - Flags: review?(bugs)
Ben meant Bug 243091 by the way.
Keywords: regression
Make sure other about pages are not lost like about:, about:mozilla and about:config.
those three have been forked for a while, so no worries there
about:blank, about:buildconfig, about:cache, about:cache-entry (needs arguments) and about:credits work as well. about:about doesn't work because bug 220253 has been marked wontfix. The only other broken page is about:logo, but that doesn't work since ages.
Attached patch fix typeaheadfind as well (obsolete) — Splinter Review
This fixes bug 243386 (find as you type aka typeaheadfind) as well. Suggestion by Pike (bug 243386 comment 4): We've got to register navigator/locale. Because: http://lxr.mozilla.org/mozilla/source/extensions/typeaheadfind/src/nsTypeAheadFind.h#71 70 #define TYPEAHEADFIND_BUNDLE_URL \ 71 "chrome://navigator/locale/typeaheadfind.properties"
Attachment #148351 - Attachment is obsolete: true
Attachment #148351 - Flags: review?(bugs)
Comment on attachment 148501 [details] [diff] [review] fix typeaheadfind as well Mike, I guess you can review it somewhat faster than Ben... See comment 1 and comment 6 for explanation.
Attachment #148501 - Flags: review?(mconnor)
Blocks: 243386
Comment on attachment 148501 [details] [diff] [review] fix typeaheadfind as well did these changes land on the branch yet?
Attachment #148501 - Flags: review?(mconnor) → review+
> did these changes land on the branch yet? Yes, they were part of Ben's checkin from 2004-05-16 11:16: http://bonsai.mozilla.org/cvsgraph.cgi?file=mozilla/browser/extensions/package-fixup/jar.mn
Whiteboard: checkin0.9
NO! this is the wrong fix. Please back it out of the trunk and branch!!!!
> NO! this is the wrong fix. Please back it out of the trunk and branch!!!! It wasn't checked in yet, neither trunk nor branch. Can you explain what's wrong with the fix, please?
Whiteboard: checkin0.9
Comment on attachment 148501 [details] [diff] [review] fix typeaheadfind as well All right, I just saw your patch in bug 243386. So this is obsolete.
Attachment #148501 - Attachment is obsolete: true
Removing dependency to bug 243386.
No longer blocks: 243386
Comment on attachment 148351 [details] [diff] [review] patch Ben, is this correct? Or has the fix to be something like you did in bug 243386? Explanation is in comment 1.
Attachment #148351 - Attachment is obsolete: false
Attachment #148351 - Flags: review?(bugs)
Attached patch better patchSplinter Review
Make about:plugins be packaged into global, not communicator.
Assignee: steffen.wilberg → bugs
Attachment #148351 - Attachment is obsolete: true
this didn't make sense to me the first time I read it, it still seems wrong, I don't remember thinking this was OK at any point. Maybe I set the flag on the wrong bug? in any case, mea culpa
Attachment #148351 - Flags: review?(bugs)
Comment on attachment 148983 [details] [diff] [review] better patch >Index: xpfe/global/resources/content/plugins.html >=================================================================== >+ var pluginsbundle = strBundleService.createBundle("chrome://communicator/locale/plugins.properties"); >+ var regionbundle = strBundleService.createBundle("chrome://communicator-region/locale/region.properties"); >+ >+ document.writeln("<title>" + pluginsbundle.GetStringFromName("title_label") + "<\/title>"); >+</script> >+<link rel="stylesheet" type="text/css" href="chrome://communicator/skin/plugins.css"> This doesn't work as long as plugins.properties and region.properties don't exist. plugins.css would be helpful as well.
Attached patch patch, part 2Splinter Review
This is also required, in addition to "better patch" Mike, can I get a quick review from this so I can check all this in on the trunk?
Whiteboard: fixed-aviary1.0
This seems fixed to me. Close?
its not fixed on trunk yet
I believe at least the blocking0.9+ could be removed then
Why didn't make the patch it onto the trunk, as comment #18 suggested? Or fell it off the radar?
the patch needs SR to land on trunk.
Just an FYI, there seems to be an issue with the about:plugins fix, on AVIARY. It seems that something has changed with the about:plugins that causes all themes other than the default theme to not use the stylesheets. The page shows up as completely plaintext. In addition, if you switch to a new theme without restarting the browser, and then type in about:plugins and hit return... Firefox crashes instantly :( I can open a new bug for the latter if you want, but the first one seems like a problem that perhaps this patch could be changed to accomadate? Or if it's simply a new .css file, then perhaps put out a notice to all the theme authors somewhere?
Forgot to mention, sorry, I'm using the Official 0.9 build (installer version).
Yes, theme authors need to fix their themes. I already made a post in the themes forum: http://forums.mozillazine.org/viewtopic.php?t=85200 I can't reproduce the crash with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Firefox/0.9 (Steffen).
Could be fixed in the past couple days. I'll give a build today or tomorrow a spin and let you know. In the meantime, anyone else who's using the Official, can you confirm it? You have to make sure to hit "Use Theme" then just close the Theme Manager, and DON'T restart Firefox before going to about:plugins.
Okay, it's not with every theme. Doodle (Classic) is one that does it ALWAYS though. As well as Firefox Modern from what I can tell. There's another anomally too with themes that I've noticed, but that's not related to about:plugins at all, so that's a new bug. If you could try downloading and using Doodle (Classic) though and see if you can reproduce the error, that would be cool.
just tested with the latest trunk (not the installer version): Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040616 Firefox/0.8.0+ with a fresh .firefox DIR no extensions/themes and about:plugins still does not work. HTH
Tim: sorry, no crash with that theme as well. Colin: that's why this bug isn't marked as fixed. It's only fixed on the branch, which includes FF 0.9, but not on the trunk. See comments 20, 21, 23, 24. Please file new bugs if you have any issues other than about:plugins not working in trunk builds (that's what this bug is about yet), or being unstyled in branch builds with non-default themes (theme authors need to fix this).
Attachment #148983 - Flags: review?(mconnor)
Attachment #148983 - Flags: review?(mconnor) → review+
Thanks Mike, I'll check this in later on this afternoon.
Fixed on trunk, too.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040620 firefox 0.8.0+ 'about:plugins' works fine. Thanks!
Verified fixed 2004-06-21
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: