Closed
Bug 86287
Opened 24 years ago
Closed 23 years ago
CSSPrimitiveValue gets undefined
Categories
(Core :: DOM: CSS Object Model, defect)
Core
DOM: CSS Object Model
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: andorxor, Assigned: jst)
Details
Attachments
(3 files)
|
540 bytes,
text/html
|
Details | |
|
539 bytes,
text/html
|
Details | |
|
This time is CSSPrimitiveValue is evaluated before alert is called. CSSPrimitiveValue stays defined.
609 bytes,
text/html
|
Details |
If CSSPrimitiveValue (and its constants like CSSPrimitiveValue.CSS_PX) are
defined seems to depend on the context CSSPrimitiveValue is evaluated in.
I'll attach three examples which show that a simple alert("") statement
undefines CSSPrimitiveValue if it hasn't been already evaluated once.
The different Mozilla versions seem to behave differently. The old Netscape6
doesn't seem to define CSSPrimitiveValue at all in this examples but behaves in
more complex examples better than the current version.
|
Reporter | |
Comment 1•24 years ago
|
||
|
|
Reporter | |
Comment 2•24 years ago
|
||
|
|
Reporter | |
Comment 3•24 years ago
|
||
|
||
Comment 4•24 years ago
|
||
Over to DOM Style. This is _very_ weird behavior.... Seeing it with Linux
build 2001-06-15-21.
Status: UNCONFIRMED → NEW
Component: DOM Level 0 → DOM Style
Ever confirmed: true
QA Contact: desale → ian
|
||
Comment 5•24 years ago
|
||
Compare bug 86659, where the addition of an alert changes the DOM behavior.
|
|
||
Comment 6•23 years ago
|
||
This worksforme in a current build. Stephan, could you retest and resolve
worksforme if you are no longer seeing the bug?
|
|
Reporter | |
Comment 7•23 years ago
|
||
Thanks, it worksforme. Tested with release 0.9.5
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•