Open
Bug 340111
Opened 20 years ago
Updated 3 years ago
Error console should say something different for unsupported but standard CSS
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: jason.barnabe, Unassigned)
Details
Right now, if you visit a site that uses CSS that is standard but unsupported in Gecko (ex: display: inline-table), you get the message
Error in parsing value for property 'display'. Declaration dropped.
This is confusing to web developers because it leads them to believe that "inline-table" is not a valid value for "display". The same goes for unsupported properties
Unknown property 'border-radius'. Declaration dropped.
For unsupported yet standard properties and values, we should instead say something along the lines of
Property 'border-radius' not yet supported in Firefox. Declaration dropped.
Updated•20 years ago
|
Assignee: nobody → dbaron
Component: Error Console → Style System (CSS)
Product: Firefox → Core
QA Contact: javascript.console → ian
Version: unspecified → Trunk
Hmm okay, file a bug if you must, but this is going to miss Firefox 2 (1.8 branch) and I sure hope we'd be able to have complete CSS 2.1 support by Firefox 3.
Also, does it perhaps belong under "error console" ? I'm not familiar with how the code works, but that'd be my guess for component.
Component: Style System (CSS) → Error Console
Component: Error Console → Style System (CSS)
Oops, sorry David, I didn't mean to change the component :s
Callek expressed interest in this earlier.
Comment 3•20 years ago
|
||
>I sure hope we'd be able to have complete CSS 2.1 support by Firefox 3.
Well, considering CSS2.1 is not yet a Technical Recomendation, (nor even a last call, it was reverted to a Working Draft) currently. We can _not_ have complete support of it just yet.
As I expressed initially, I am interested in this bug (Thanks for the CC); however I feel this may best be completed as an extension to Firefox (which watches the error console's actual errors) rather than as something created internally to send different messages.
Comment 3 doesn't make much sense, either on its comments about CSS 2.1 or about how to implement this.
Assignee: dbaron → nobody
QA Contact: ian → style-system
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•