Closed
Bug 316200
Opened 19 years ago
Closed 19 years ago
proposition to give css parsing (and recognition errors) on console severity "Warning"
Categories
(Toolkit Graveyard :: Error Console, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 264162
People
(Reporter: lucash, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5
Many sites (and sites that I create in particular) use large number of techniques for crossbrower compatibility. For example css
* {
-moz-box-sizing: border-box;
box-sizing: border-box;
}
box-sizing is standard property but FF doesn't support it in favour of
-moz-box-sizing. But why dropping of box-sizing cause error message instead of warning.
div.Clazz1 {
display: inline-block;
display: table-cell;
}
this construct in some cases gives desired result for compatibilty. But again dropping unknown "inline-block" property value gives error message.
But when error occured in js processing than whole processing thread is terminated for given declaration, function, file, event handling etc.
Just ignoring (dropping) unknown properties and values means that this kind of
css errors are simply warning, not errors. But if they are threated as errors than it is very difficult to distinguish them from really serious showstopping errors (for example js malfunction).
Conclusion: I propose to give css dropping unknown properties and value errors
serverity "warning" on jsconsole
Reproducible: Always
Updated•19 years ago
|
Summary: proposiotion to give css parsing (and recognition errors) on console severity "Warning" → proposition to give css parsing (and recognition errors) on console severity "Warning"
Duplicate of bug 316149 -> bug 265871?
Reporter | ||
Comment 2•19 years ago
|
||
..sort of. Seams really like duplicate
hadn't time to carefully search bugs before posting.
Comment 3•19 years ago
|
||
This was fixed by a patch for bug 264162.
*** This bug has been marked as a duplicate of 264162 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
Assignee | ||
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•