Closed
Bug 62673
Opened 24 years ago
Closed 22 years ago
DOMImplementation incorrectly reports conformance to "CSS" module
Categories
(Core :: DOM: CSS Object Model, defect, P3)
Core
DOM: CSS Object Model
Tracking
()
RESOLVED
FIXED
mozilla1.0.1
People
(Reporter: david, Assigned: jst)
Details
(Keywords: dom2)
Attachments
(1 file)
819 bytes,
text/html
|
Details |
DOMImplementation.hasFeature("CSS", "2.0") returns true, claiming compliance with the DOM Level 2 CSS specification. But, as the bugs shown by the attached test case demonstrate, it is not compliant, and the method should return false. See also bug #62607, bug #62611, bug #62612, bug #62613
Reporter | ||
Comment 1•24 years ago
|
||
No browser is 100% fully compliant! Bugs wil be fixed in time, so there's no reason to state that it should not return 2.0. And a lot of people are working very hard to fix this kind of human errors. Just give them some air! Friendly, HJ.
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → mozilla1.0
Updated•23 years ago
|
Component: DOM Level 2 → DOM Style
Comment 3•23 years ago
|
||
Taking QA Contact on all open or unverified DOM Style bugs...
QA Contact: vidur → ian
Comment 4•23 years ago
|
||
Question: Is bug #30534 related? This may be a dup of the other one.
Comment 5•23 years ago
|
||
David, all the bugs you cited when opening this are fixed... Is the idea that you would like us not to claim to support CSS2 unless we fully support all of DOM 2 CSS?
Comment 6•23 years ago
|
||
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 7•22 years ago
|
||
I think the conclusion in bug 30534 was that we support the CSS module at a level where saying we don't support it makes no sense.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•