Bug 17166
Summary: | Test (and fix) complex resource invalidations (symbol nesting, CDF symbols) | ||
---|---|---|---|
Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
Component: | SVG | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | zimmermann |
Priority: | P2 | Keywords: | NeedsReduction |
Version: | 528+ (Nightly build) | ||
Hardware: | Mac | ||
OS: | OS X 10.5 | ||
Bug Depends on: | 15394 | ||
Bug Blocks: |
Eric Seidel (no email)
Test (and fix) complex resource invalidations (symbol nesting, CDF symbols)
WildFox is fixing notifyResourceParentIfExistant (now called invalidateResourcesInAncestorChain) as part of bug 15394.
I pointed out two possible test cases which might fail with his changes. Neither is particularly important, but this bug exists so we can track writing real tests and checking behavior against other browsers.
1. Nested <symbol> elements:
<symbol id="one"><symbol id="two"><rect/></symbol></symbol>
<use xlink:href="#one">
<use xlink:href="#two">
When you modify the rect, do both symbols get invalidated?
2. SVG resource-bearing elements containing CDF content:
<symbol>
<foreignObject>
<div>
<svg>
<rect>
</svg>
<foreignObject>
</div>
</symbol>
When you invalidate the inner rect, does the outer symbol get properly invalidated? (of course, I'm not even sure that if you change the <div> inside the <fO> we correctly invalidate the symbol.)
The first thing we need here is to turn these examples into real test cases.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Nikolas Zimmermann
If there are still bugs, individual ones should be filed, this is way too generic - should be closed. Nested symbols are also tested extensively.