Open
Bug 388859
Opened 17 years ago
Updated 2 years ago
duplication between setting |inherited| and Check*Callback
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
Future
People
(Reporter: dbaron, Unassigned)
Details
Attachments
(1 file)
33.90 KB,
patch
|
Details | Diff | Splinter Review |
In bug 388548 comment 3, bzbarsky wrote: > I really wish we didn't duplicate logic like this between the check > callbacks and the actual computation. :( We can avoid this duplication by initializing |aInherited| better and not setting it in nsRuleNode::Compute*Data in the cases where it's already set based on that initialization. We should probably have some assertions to verify things, though.
Reporter | ||
Updated•17 years ago
|
Assignee: dbaron → nobody
Status: ASSIGNED → NEW
Target Milestone: mozilla1.9beta1 → Future
Reporter | ||
Comment 1•17 years ago
|
||
Here's what I was thinking, roughly. This achieves the assertions by making parentdata_ null when we shouldn't be using it, but there are a bunch of places where we dereference things in parentData because we might use them. So it crashes, probably because of that, although I haven't checked. I'm not going to work further on this now; I can't justify making it a priority.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•