Closed
Bug 35621
Opened 24 years ago
Closed 22 years ago
[trk] (DOM2 CSS) CSS2Properties
Categories
(Core :: DOM: CSS Object Model, defect, P3)
Core
DOM: CSS Object Model
Tracking
()
VERIFIED
FIXED
mozilla1.1alpha
People
(Reporter: jst, Assigned: jst)
References
(Depends on 1 open bug)
Details
(Keywords: dom2)
No description provided.
Comment 1•24 years ago
|
||
Nominating nsbeta2. DOM2 CSS must FC (for whatever CSS2 features we will support) for nsbeta2 and provide a solid web application platform. Johnny's working on these and in many cases already has code ready to land; the rest should be finished ASAP and managed by exception.
Keywords: nsbeta2
Assignee | ||
Comment 2•24 years ago
|
||
This is implemented in mozilla, the only thing that remains is to remove the inheritance from CSS2Properties and make CSS2Properties a co-interface to CSSStyleDeclaration, but this is completely transparent to script writers and thus not required for nsbeta2, removing keyword, and setting milestone to M19.
Assignee | ||
Comment 3•24 years ago
|
||
Pushing off to Future, this might get fixed if we do a interface freese for the DOM intefaces so we might haveto pull this back...
Target Milestone: M19 → Future
We could use an implementation (in ECMA binding anyway) of CSSStyleDeclaration.getPropertyCSSValue() so that we can get a Rect object for the clip style property. Right now, all we get is the DOMString of the clip value (e.g., "rect(0px 50px 100px 0px)") which makes it very cumbersome to parse for reading individual edge values. In comparison, the NN4 layer object had a suite of clip-related properties (clip.top, clip.right, clip.width, etc.); IE5+ provides individual edges through the currentStyle object (clipTop, clipRight, etc.). The way I read DOM2, we should be able to get edge values like this: [elemRef].style.getPropertyCSSValue("clip").getRectValue().top Not particularly smooth, but it's better than parsing the clip string.
Updated•24 years ago
|
QA Contact: vidur → ian
Updated•24 years ago
|
Component: DOM Level 2 → DOM Style
Comment 5•24 years ago
|
||
Taking QA Contact on all open or unverified DOM Style bugs...
Comment 6•23 years ago
|
||
Nominating this bug for nsbeta1 on behalf of gerardok@netscape.com.
Keywords: nsbeta1
Whatever the importance of this work, there isn't time to start and complete it for nsbeta1. Marking nsbeta1- and setting Target Milestone to 0.9.2 for reevaluation after beta.
Assignee | ||
Comment 8•23 years ago
|
||
Moving to mozilla0.9.3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Assignee | ||
Comment 9•23 years ago
|
||
Pushing to mozilla0.9.5
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Assignee | ||
Comment 10•23 years ago
|
||
Pushing to mozilla0.9.7
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Assignee | ||
Comment 11•23 years ago
|
||
No a mozilla 1.0 stopper.
Target Milestone: mozilla0.9.7 → mozilla1.1
Comment 12•22 years ago
|
||
Um, so what exactly is left to do here again?
Comment 13•22 years ago
|
||
Hmmm... now that all our CSSDeclarations implement CSS2Properties and even do it almost correctly, not much...
Comment 14•22 years ago
|
||
So can we resolve this then? If there are any issues left, maybe a separate, specific bug would be good, because this bug surely is confusing...
Comment 15•22 years ago
|
||
Yep.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•