308583 - Error in parsing value for property 'width'. Declaration dropped.

Status: RESOLVED INVALID

(Toolkit Graveyard :: Error Console, defect)

Description

[Dixson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

I'm noticing lots of erros in the Javaconsole that say:
Error in parsing value for property 'width'.  Declaration dropped.

Also lots of the same for other properties such as height.

The JS code does properly get the property value such as screen height.

Reproducible: Sometimes

Steps to Reproduce:
1. visit some different sites using Firefox 1.5 beta
2. view the JavaScript console
3. note all the various "error in parsing" errors in the log.

Actual Results:  
results ok but lots of errors in the JavaScript console are concerning. Perhaps
something else is wrong somewhere.

Expected Results:  
No JavaScript console errors

Comment 1

[Kevin Brosnan]

As this is written it is not a valid bug as it is too vague. There are reasons
why Firefox would be vaild in dropping width rules.

Comment 2

[Josh Birnbaum]

Dixson, can you give us an example?  The JavaScript console can show errors
caused by bad javascript internal to firefox, but usually it shows errors
resulting from the websites you visit.  Since most websites don't correctly
follow the specs, you end up with a lot of console entries.

Comment 3

[Dixson]

I'll look around and see if I can find some specific examples to pass along. 
The reason I reported this was because at the time I switched over to FF 1.0.6
and these same errors did not appear in that console, only with 1.5b1.

Also it would help if someone could explain specifically what this error message
means: "Error in parsing value for property 'width'.  Declaration dropped".

What specifically is FF complaining about there?  What does it mean about an
error "parsing" value for the property? And, what does it mean by "declaration"
dropped?  In the examples where I saw the error in the console the JS was still
apparently returning the correct property value, so it seemed strange that it
was reporting errors in the console in the first place with the results
seemingly working anyway.

Comment 4

[Josh Birnbaum]

That particular message is a CSS parsing error.

Comment 5

[Nickolay_Ponomarev]

The reporting of CSS parsing errors is a new feature of Gecko 1.8. It complains
about bad CSS on sites, e.g. it would say that if you used "width: asdf" or
"width: 10" (without specifying units).

There's a bug to allow filtering those errors, and a nice extension, Console2,
which implements that.

No bug here. Marking invalid.

Comment 6

[Tanner M. Young [:tmyoung]]

Resetting QA contact to default.