Alternatively click Help >Troubleshooting Information, then click the
"Open Containing Folder" button which will open your profile folder.
Incide that folder there should be a folder labeled Chrome. The
userChrome.css, I think, doesn't exist by default, but if one has been
created it will be in that Chrome folder. If it's not there, just
create an empty text file in the folder and name it userChrome.css.
(Note the uppercase C in the file name.)
Dave Pyles
> Ok, so the mystery is a little bit solved. There is no chrome folder
> in the profile folder. It shouldn't make a difference but this was a
> Fx4 install that upgraded over Fx 3.6.15. For whatever reason, it
> removes the chrome folder. I can manually add one and things work but
> that's odd. For what it's worth, this is not pointing to the usual
> location but to a custom location where the profile cannot be deleted.
> I'll just leave it at that. Now that I have a handle on it, I'll do
> some experimentation with it.
>
If the chrome folder existed in 3.x, it would have been copied unless
you created a new FF4 profile. Then it would have been left up to you
to copy over what you wanted from 3.x to 4. I've never seen FF remove
anything in the profile, so I doubt that happened.
Terry R.
--
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
If that button is on a toolbar, then it should be removable back to the
toolbar Pallet by Drag&Drop.
--
Ron K.
Who is General Failure, and why is he searching my HDD?
Kernel Restore reported Major Error used BSOD to msg the enemy!
Sounds like a better solution would be locking down the feature through
what ever replaced CAPS in the Gecko backend.
Yes, I noticed that also. I guess if it isn't needed, it isn't created.
Who needs a bunch of empty folders?
For now, these style overrides should work:
#bookmarksMenu,
#PersonalToolbar { display:none !important; }
Good luck.
--
Sailfish - Netscape/Mozilla Champion
Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/
Rare Mozilla Stuff: http://www.projectit.com/
#toolbar-context-menu menuitem:not([id="toggle_toolbar-menubar"]), /*
Hide all menu items except menubar */
#toolbar-context-menu menuseparator /* Hide all menuseparators */
{ display:none !important;}
Because CSS is Cascading, the order of rules is important. In principal,
rules are arranged from the Global to the specific to reduce instances of
undesired results.
#BrowserPreferences radio[pane="paneSync"] { display: none !important; }
I've tried using this one and the ones above together and they seem to
work fine.
There are a couple of ways you could get around this. The easiest would
be to write-protect the profile chrome/ folder and the files within it
with Admin permissions.
A less secure method would be to add another style override to your
userChrome.css file and one to your userContent.css (may need to be
created) file as follows:
userChrome.css Style Override:
menuitem#troubleShooting { display: none !important; } /* Removes Help
Troubleshooting menu option */
userContent.css Style Override:
div#contents button { display: none !important; } /* Removes "Open
Containing Folder" button from about:support page */
Lastly, I should mention that there a innumerable ways an enterprising
individual may find to circumvent your overrides, these are really meant
to provide the less-enterprising ones :)
Lastly, I should mention that there are innumerable ways an enterprising
individual may find to circumvent your overrides, these are really meant
to prevent the less-enterprising ones.
>>> Well, as luck would have it, removing #BrowserPreferences
>>> radio[label="Sync"] {display: none! important;} makes everything else
>>> but Menu Bar disappear but then I lose hiding Sync in options. LOL. Is
>>> there an entry that just removes "Bookmarks Toolbar" from that context
>>> menu that I could try? I could live with the other being there but
>>> dammit, I'm gonna exhaust every option (and probably you too!).
>>> Cheers.
>>>
>> That "#BrowserPreferences ..." override came from somewhere else. The
>> one I gave you before was:
>>
>> #BrowserPreferences radio[pane="paneSync"] { display: none !important; }
>>
>> I've tried using this one and the ones above together and they seem to
>> work fine.
>
> Ron K pointed out that it might be related to the order. I'm going to
> do some re-arranging to put the global stuff first and less specific
> stuff last. I didn't realize that might have been the case.
>
> - Thee Chicago Wolf [MVP]
A clarification of my comment on ordering. CSS works much like outlining
of a document. Where each level of sub-rules applies only to that
sub-section, by becoming more specific and can over ride rules from the
parent containing rule set.
Good luck.
TIA
There were a couple of omissions and one misplaced rule that caused some
issues. Below is a re-formatted version that seems to work on my system
using the default theme.
Also, another good place to check to see if you may have some problems
with your userChrome.css entries is the Error Console, Tools>Error Console.
I hope this helps.
#addonsMgrGroup,
#bookmarksMenu,
#bookmarksToolbarFolderMenu,
#bookmarks-menu,
#component-bar,
#context-blockimage,
#context-bookmarkframe,
#context-bookmarklink,
#context-bookmarkpage,
#context-keywordfield,
#context-sendaudio,
#context-sendimage,
#context-sendlink,
#context-sendpage,
#context-sendvideo,
#context-setDesktopBackground,
#context-setWallpaper,
#defaultBrowserButton,
#organizeBookmarksSeparator,
#popupPolicyButton,
#toolbar-context-menu menuitem:not([id="toggle_toolbar-menubar"]),
#toolbar-context-menu menuseparator,
#sync-button,
#sync-setup,
#sync-setup-appmenu,
#sync-status-button,
#sync-syncnowitem-appmenu,
menuitem#troubleShooting,
#BrowserPreferences radio[pane="paneSync"],
menu[label="Tools"] menuitem[label="Sync Now"] {display: none
!important;}
PS: Just a reminder, you may want to create and add the following
override to your userContent.css file to ensure that the Open
userChrome.css file button is hidden in the event that someone enters,
about:support in the URLbar:
div#contents button { display: none !important; }
--