Closed Bug 654470 Opened 14 years ago Closed 13 years ago

userChrome.css modifications fail

Categories

(Firefox :: General, defect)

4.0 Branch
x86
Windows 7
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: l.breyers, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 With userChrome.css in the following location: /* C:\Users\Admin\AppData\Roaming\Mozilla\Firefox\Profiles\9ke4cuze.default\chrome\userChrome.css*/ And the file itself containing this: /* Do not remove the @namespace line -- it's required for correct functioning */ @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* Gets rid of fullscreen dropdown toolbar */ #fullscr-toggler {display: none !important;} /* Moves vertical scrollbar out of view /* browser[type="content-primary"], browser[type="content-targetable"] { overflow-y: scroll; margin-right: -12px; /* 12px == width of my scrollbar */ } Neither of them work in firefox anymore. I've tested this on multiple computers who had these modifications working before. It appears as if firefox doesnt respond to userChrome.css anymore, as nothing seems to affect it. Reproducible: Always
Component: Build Config → General
QA Contact: build.config → general
I've also noticed this with userContent.css, FF doesnt seem to respond to it anymore. Is there a new .css file/format that FF4 uses, or is FF4 just fundamentally broken?
Version: unspecified → 4.0 Branch
*User Agent:* Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110513 Firefox/6.0a1 *Works for me:* The fullscreen dropdown toolbar works for me. But, the vertical scrollbar out of view doesn't.
does it still fail?
Summary: Firefox does not respond to userChrome.css modifications anymore → userChrome.css modifications fail
Whiteboard: [closeme 2012-07-08]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2012-07-08]
You need to log in before you can comment on or make changes to this bug.