Closed Bug 74759 Opened 24 years ago Closed 23 years ago

Improve contents of default userChrome.css

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
mozilla0.9.5

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

(Keywords: css-moz, css1, Whiteboard: [Hixie-PF])

Attachments

(1 file, 1 obsolete file)

The current contents make us look like Irix. Is this a good thing?
Depends on: 37642
Interesting example contents: menubar { display: none; } toolbar { display: none; } location { display: none; } statusbar { display: none; } extrachrome { display: none; } directories { display: none; } title { display: none; } status { display: none; } #taskbar { display: none; }
the default userChrome.css file should probably set the default namespace to XUL, too, to avoid weirdness.
Component: Browser-General → Style System
Keywords: css-moz, css1, mozilla1.2
QA Contact: doronr → ian
Whiteboard: [Hixie-PF]
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.2
pushing out to mozilla0.9.3. No way I can get this done for 0.9.2 Going to take this to the newsgroup for some ideas...
Target Milestone: mozilla0.9.2 → mozilla0.9.3
ccing sfraser for his comments. Thoughts?
Keywords: mozilla1.0, patch, review
Easier to explain and less error-prone to have explicit namespaces: +@namespace html url(...); +@namespace xul url(...); ^^^ xul|tag { } html|tag { }
All the tags involved are XUL ones. Should I still attach "xul|" to everything and not declare xul to be the default namespace? While I can do that, it seems like it would just make the file more confusing to the average non-XML-namespace-clueful person.
You are right, no need to add further clutter since there is already a prominent separation user[Chrome|Content].css and that is more than enough in general. Only power users may go into the trouble of mixing things up, and if they can do that, they can as well mess with namespaces...
pushing out.... Comments and reviews still welcome.
Target Milestone: mozilla0.9.3 → mozilla0.9.5
I'm unsure about the user of 'pt' units in screen stylesheets, wouldn't pixels be a better idea?
Well... I don't know. I avoid "px" like the plague because I use a single Mozilla profile that lives in AFS on a bunch of computers with fairly varying screen resolutions. "pt" tend to give such better results that I never even thought of specifying a font size in "px". If you feel that for the average user "px" would be better, I'll change that, of course. :)
Attachment #42460 - Attachment is obsolete: true
So... anyone care to review that patch or tell me something definite one way or the other on the px/pt issue? Should I just push this out to Future if no one is willing to review it?
Looks good, and that will make one bug less from bugzilla... r=rbs
Comment on attachment 42461 [details] [diff] [review] Oops. This is the real patch. Ignore that first one. :) sr=alecf
Attachment #42461 - Flags: superreview+
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: