Closed
Bug 112093
Opened 23 years ago
Closed 23 years ago
Computed style getPropertyCSSValue() bustage/regression
Categories
(Core :: DOM: CSS Object Model, defect)
Core
DOM: CSS Object Model
Tracking
()
RESOLVED
DUPLICATE
of bug 109523
People
(Reporter: mike, Assigned: jst)
References
()
Details
(Keywords: dom2, regression)
Somewhere between 0.9.5 and builds up to at least 20011126xx, calling getPropertyCSSValue() on a computed style object has regressed. Previously, the call returned a valid CSSValue, but now it throws an unimplemented exception. See the page in the URL field for a basic test case. I can probably provide more debug if needed. This is occuring on Linux/2001112308 and Windows/2001112603
Reporter | ||
Updated•23 years ago
|
Keywords: dom2,
regression
Assignee | ||
Comment 1•23 years ago
|
||
bz?
Comment 2•23 years ago
|
||
Yep. You're getting "top" for a statically positioned element which is indeed not implemented at the moment (mostly because when I reimplemented all the positioning property stuff to actually do more-or-less-correct calculations there was some disagreement as to what the positioning properties should do for statically positioned elements). dup of "Implement getComputedStyle for non-computed values" *** This bug has been marked as a duplicate of 109523 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•23 years ago
|
||
bz, just to clarify: when you reimplemented the positioning property stuff, it broke getting the position properties (top, left, etc) for some, or all elements? Note that it *was* working in 0.9.5.
Comment 4•23 years ago
|
||
Just for statically positioned (non-positioned) elements. Relative, absolute, and static position work fine (better in fact). And bug 109523 _does_ have a patch to stop throwing those exceptions... :)
You need to log in
before you can comment on or make changes to this bug.
Description
•