Closed Bug 110214 Opened 24 years ago Closed 15 years ago

some stylesheets imported multiple times

Categories

(SeaMonkey :: Themes, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: hewitt, Unassigned)

Details

(Keywords: perf, Whiteboard: [need info])

DOM Inspector has a view which lets you see which stylesheets are loaded in a particular document. While I was playing with this as I implemented it this week, I discovered that some documents load stylesheets multiple times, which means those rules will actually be looked at more than once during style resolution. As an example, point Inspector at chrome://messenger/content/ and you will see that chrome://messenger/skin/folderMenus and chrome://communicator/skin/tasksOverlay.css are imported twice.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.9
There's another bug claiming multiple loads of certain chrome files! This other bug was filed by: bugs4hj@netscape.net but I can't find it at this moment.
Target Milestone: mozilla0.9.9 → mozilla1.0
Keywords: nsbeta1, perf
Nav triage team needs info: What is the effect on the MachV user? Are you sure this is happening? Hyatt had a similar bug that he doubted was actually multiple loads.
Whiteboard: [need info]
Nav triage team: nsbeta1-
Keywords: nsbeta1nsbeta1-
Mass-moving all Navigator team 1.0 nsbeta1- bugs to 1.1
Target Milestone: mozilla1.0 → mozilla1.1
Product: Core → SeaMonkey
Assignee: hewitt → nobody
Status: ASSIGNED → NEW
QA Contact: pmac → themes
Target Milestone: mozilla1.1alpha → ---
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.