Closed Bug 1177563 Opened 10 years ago Closed 10 years ago

add regression test to ensure we don't fall off the shared rule processor optimized path

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla42
Tracking Status
firefox42 --- fixed

People

(Reporter: heycam, Assigned: heycam)

References

Details

Attachments

(1 file)

In bug 77999 we share rule processors across documents that use the same set of agent/user style sheets. We should add a regression test to ensure that we don't accidentally stop sharing rule processors for the simple case of having a couple of blank tabs open.
Attached patch patchSplinter Review
Assignee: nobody → cam
Status: NEW → ASSIGNED
Attachment #8626355 - Flags: review?(dbaron)
Summary: add regression test to ensure we don't fall of the shared rule processor optimized path → add regression test to ensure we don't fall off the shared rule processor optimized path
Comment on attachment 8626355 [details] [diff] [review] patch Please rev the IID for nsIDOMWindowUtils. r=dbaron with that Is it worth testing that winUtils.hasSharedRuleProcessor(Ci.nsIStyleSheetService.AGENT_SHEET) is false in some case as well? (Maybe on the AUTHOR_SHEET level, with a tab that's not about:blank and has a style element?) (Having a test that tests that hasSharedRuleProcessor returns false in some case also helps test hasSharedRuleProcessor itself.)
Attachment #8626355 - Flags: review?(dbaron) → review+
Yes, that's a good idea. I've added two additional checks to the test -- that the AUTHOR_SHEET rule processor is not shared, and that adding a new, unique sheet to the agent-level causes its rule processor to be not shared.
Flags: needinfo?(cam)
Flags: needinfo?(cam)
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: