Closed Bug 82515 Opened 24 years ago Closed 24 years ago

not displaying CSS

Categories

(Core :: DOM: CSS Object Model, defect)

x86
Windows ME
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: nardus, Assigned: jst)

References

()

Details

I tried putting the CSS both inline and in an external file, but nothing. It worked on previous nightlies, and it works on IE. The strange thing, is that other sites that use CSS work allright (e.g.: www.ddmsa.com, it works perfectly).
WFM on May 23 build 2001052304 under Win2000 (SP2).
reporter, what build are you using? what exactly is not working? please read: http://www.mozilla.org/quality/bug-writing-guidelines.html In the above URL both <script> and <style> tags are missing type= attribute which is required by HTML standard. The inline style properties like for example "top:20; left:176; width: 445" have some numbers specified, but what those numbers are? These CSS properties accept length which should be specified in em, ex, px, in, cm, mm, pt or pc. Numbers by themselve mean nothing (except for 0). For reference see: http://www.w3.org/TR/REC-CSS2/syndata.html#value-def-length
WFM also, 2001052404 Win2K
The I assume the problem with this page is that the buttons at the top of the page don't fade (gradually) when you mouse over the buttons. I haven't looked at this in detail yet, but it looks like the page is using proprietary IE CSS extensions that are not supported (or don't work the same way) in mozilla. Can someone confirm?
Yes, thanks Johnny for finding the difference, I didn't notice it the first time around. The page uses style="filter:opacity(xx%)" which is an IE proprietary CSS property. The closest thing Moz has to this is the -moz-opacity property. Iván, you should be advised that the filter property is not a part of the W3C CSS Recommendation, and Mozilla doesn't and won't support it (unless it at some point becomes a part of the Spec). Of course, if that was not what you were talking about, let us know. Otherwise this bug will be marked Invalid.
WONTFIX
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.