Closed Bug 379405 Opened 17 years ago Closed 17 years ago

[FIX]"ASSERTION: Unexpected left/right/top/bottom unit" with getComputedStyle on "position: relative" element

Categories

(Core :: CSS Parsing and Computation, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla1.9alpha5

People

(Reporter: jruderman, Assigned: bzbarsky)

References

(Blocks 1 open bug, )

Details

(Keywords: assertion, testcase)

Attachments

(2 files)

Attached file reduced testcase (deleted) —
Loading http://www.dailyrotation.com/ or the reduced testcase triggers:

###!!! ASSERTION: Unexpected left/right/top/bottom unit: 'Error', file /Users/jruderman/trunk/mozilla/layout/style/nsComputedDOMStyle.cpp, line 2456
Attached patch Fix (deleted) — Splinter Review
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #263399 - Flags: superreview?(dbaron)
Attachment #263399 - Flags: review?(dbaron)
OS: Mac OS X → All
Priority: -- → P3
Hardware: PC → All
Summary: "ASSERTION: Unexpected left/right/top/bottom unit" with getComputedStyle on "position: relative" element → [FIX]"ASSERTION: Unexpected left/right/top/bottom unit" with getComputedStyle on "position: relative" element
Target Milestone: --- → mozilla1.9alpha5
Somebody should really go through and file bugs on the assertions in the CSS mochitests, since Jesse's going through and reducing all of them from more complex testcases...
Blocks: 377731
Comment on attachment 263399 [details] [diff] [review]
Fix

r+sr=dbaron
Attachment #263399 - Flags: superreview?(dbaron)
Attachment #263399 - Flags: superreview+
Attachment #263399 - Flags: review?(dbaron)
Attachment #263399 - Flags: review+
Note that this may make some xfail mochitests pass.
I doubt it, since this is not changing any behavior; just avoiding the assert when we shouldn't assert.
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Flags: in-testsuite?
Based on comment 2, I think this is already covered by a test suite.  Assertions in that test suite just don't turn anything orange.
Flags: in-testsuite? → in-testsuite+
(In reply to comment #7)
> Based on comment 2, I think this is already covered by a test suite. 
> Assertions in that test suite just don't turn anything orange.

I'm not sure it's a good idea to mark bugs in-testsuite+ if the test can't turn the tree orange. We should probably wait until bug 370767 is fixed.
Flags: in-testsuite+ → in-testsuite?
Meh, that's what we're doing everywhere else to keep track of what tests have been checked in.
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: