Closed Bug 158069 Opened 22 years ago Closed 22 years ago

CSS error with debug build when startup

Categories

(Core :: CSS Parsing and Computation, defect)

Sun
SunOS
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 139942

People

(Reporter: jerry.tan, Assigned: shliang)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1b) Gecko/20020717
BuildID:    20020715

when I startup 20020715 debug build,
there is one line error message ouput to console screen, it says that
"CSS Error (chrome://global/skin/toolbar.css :96.13): Error in parsing value for
property 'width'.  Declaration dropped."



Reproducible: Always
Steps to Reproduce:
1.startup mozilla when finish building
2.
3.

Actual Results:  duiring startup, there is an error message in the console
"CSS Error (chrome://global/skin/toolbar.css :96.13): Error in parsing value for
property 'width'.  Declaration dropped."

Expected Results:  No such error message. I can bear assert, warning message,
but dont want to see any error message during startup.
it is caused by css parser dont recognize 
/themes/classic/global/win/toolbar.css line 96:
width: none;

it dont happen before on my sparc with trunk debug build.
it also happens on win2k with 20020717 debug build.
it seems that css parser dont recognize "width=none;" now.

although remove it from toolbar.css can avoid error message duiring startup,
I think it is caused by the code change of css parser.
Component: Themes → Style System
"width: none" is invalid CSS.  All that changed in the CSS parser is that it has
started reporting errors in debug builds instead of just silently dropping
invalid CSS.

See bug 139942 for more info (in particular bug 139942 comment 8).
Blocks: 139942

*** This bug has been marked as a duplicate of 139942 ***
No longer blocks: 139942
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
I see the patch of bug 139942, it will fix this bug
so mark this bug as dup
Except that patch isn't going to be checked in.  Specific bugs should be filed
on individual errors.
You need to log in before you can comment on or make changes to this bug.