Modify ↓
Opened 17 years ago
Closed 16 years ago
#5916 closed defect (wontfix)
Internet Explorer 6 css hacks cause validation warnings
Reported by: | anonymous | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | general | Version: | 0.10.3 |
Severity: | trivial | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Firefox's WebDeveloper plugin gives following warning in trac.css.
Warning: Error in parsing value for property 'display'. Declaration dropped. Source File: http://myserver/trac/heppa/chrome/common/css/trac.css Line: 66
The offending code is this (the line starting with * html
):
@media screen { a.ext-link .icon { background: url(../extlink.gif) left center no-repeat; padding-left: 16px; } * html a.ext-link .icon { display: inline-block; } }
Attachments (0)
Change History (2)
comment:1 by , 17 years ago
Milestone: | → 0.12 |
---|---|
Summary: | Syntax error in trac.css → Internet Explorer 6 css hacks cause validation warnings |
comment:2 by , 16 years ago
Milestone: | 0.12 |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
I don't think this is a problem. CSS defines parse error recovery routines quite precisely, which can be used for things such as CSS filters. Conditional comments are IMO not a cleaner solution for this (I blogged about this topic some time ago).
Note:
See TracTickets
for help on using tickets.
That is a workaround for IE5-6 to allow the inline anchor to have padding. The "* html" causes most browsers to ignore that definition entirely since there is no element outside html, except in IE.
We should eventually move to conditional comments to allow better browsers to not have to download the IE6 workarounds and I don't remember a prior ticket on the issue so I'm targeting it at "the future." Thanks for the report.