This forum is a discussion about improving the "Forum Response - Tabs below the URL bar" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

New article / canned response

  • 32 Replies
  • Last reply by AliceWyman
  1. AliceWyman 5146 posts
    Report Abuse

    Is this a common forum response? If so, the article title should start with Forum response - according to the Create or improve common forum responses article.


    I did a forum search on userChrome.css tabs and came up with these recent support forum threads related to tab placement:

    https://support.mozilla.org/en-US/questions/1184503 How do I get the tabs back below the bookmarks toolbar (where they SHOULD be) in Firefox Quantum?

    https://support.mozilla.org/en-US/questions/1185426 Moving the tabs below the menu toolbar in Firefox 57

    https://support.mozilla.org/en-US/questions/1184899 Want a tabs on bottom add-on for FF57

    https://support.mozilla.org/en-US/questions/1184585 How can I move the open pages to the bottom instead of the top?

    https://support.mozilla.org/en-US/questions/1185495 How do I get my tabs back below the bookmark toolbar? And why the hell did you change this??? And now white on black? Unreadable. ^ Note: This last question was from a Mac user.

    Is this a common forum response? If so, the article title should start with '''Forum response - ''' according to the [[Create or improve common forum responses]] article. ----- I did a forum search on '''userChrome.css tabs''' and came up with these recent support forum threads related to tab placement: https://support.mozilla.org/en-US/questions/1184503 How do I get the tabs back below the bookmarks toolbar (where they SHOULD be) in Firefox Quantum? https://support.mozilla.org/en-US/questions/1185426 Moving the tabs below the menu toolbar in Firefox 57 https://support.mozilla.org/en-US/questions/1184899 Want a tabs on bottom add-on for FF57 https://support.mozilla.org/en-US/questions/1184585 How can I move the open pages to the bottom instead of the top? https://support.mozilla.org/en-US/questions/1185495 How do I get my tabs back below the bookmark toolbar? And why the hell did you change this??? And now white on black? Unreadable. ^ '''Note:''' This last question was from a Mac user.
    Modified by AliceWyman on
  2. AliceWyman 5146 posts
    Report Abuse

    By the way, Firefox 56 had tabs on top, above the address bar. Screenshot:

    Fx56-TabsLocation

    The people asking about the "change" in Firefox 57 must have been using an add-on that's notcompatible with Quantum, e.g.,:

    https://addons.mozilla.org/en-US/firefox/addon/tabs-on-bottom/

    Related forum thread, from Jan 2016: https://support.mozilla.org/en-US/questions/1106927 I want my tabs on bottom again, how do I do it? (quote from the-edmeister 1-31-2016)

    "Tabs on Top" has been the default, (with no option as with earlier versions), in Firefox since the Firefox 29 version was released in April 2014. Since then users have needed an add-on or "userChrome.css code" to move the tabstrip to the "bottom", so if that quit just now it is probably due to an add-on not being compatible with the new Firefox version.
    By the way, Firefox 56 had tabs on top, above the address bar. Screenshot: ;[[Image:Fx56-TabsLocation]] The people asking about the "change" in Firefox 57 must have been using an add-on that's notcompatible with Quantum, e.g.,: https://addons.mozilla.org/en-US/firefox/addon/tabs-on-bottom/ Related forum thread, from Jan 2016: https://support.mozilla.org/en-US/questions/1106927 I want my tabs on bottom again, how do I do it? (quote from the-edmeister 1-31-2016) <blockquote>"Tabs on Top" has been the default, (with no option as with earlier versions), in Firefox since the Firefox 29 version was released in April 2014. Since then users have needed an add-on or "userChrome.css code" to move the tabstrip to the "bottom", so if that quit just now it is probably due to an add-on not being compatible with the new Firefox version.</blockquote>
  3. Tonnes 63 posts
    Report Abuse

    Yes it is, and it was renamed accordingly and added to common forum responses. Also see this thread.

    Yes it is, and it was renamed accordingly and added to ''common forum responses''. Also see [https://support.mozilla.org/en-US/kb/forum-response-legacy-add-ons-webextensions/discuss/7311 this] thread.
  4. AliceWyman 5146 posts
    Report Abuse

    This response says, The following "moving tabs below the URL bar" procedure only works on Linux and Windows. It does not work on Mac OS X. ... but see this thread (linked above) posted by "jmazzeo", a Mac user: https://support.mozilla.org/en-US/questions/1185495 How do I get my tabs back below the bookmark toolbar? And why the hell did you change this??? And now white on black? Unreadable.

    The instructions by jscher2000 worked for the Mac user in /questions/1185495 so the following solution should either be added to this response or else this response should link to /questions/1185495:

    jscher2000 said

    (1) Tab bar position You can use a custom style rule in a userChrome.css file to rearrange the toolbars. (A) You need to create a new chrome folder in your profile folder. This article has the steps for that (#1, #2, and optionally #3) https://www.userchrome.org/how-create-userchrome-css.html (B) Download the following file and move it into that chrome folder: https://www.userchrome.org/samples/userChrome-tabs_on_bottom.css (C) Rename the file to just userChrome.css The next time you quit Firefox and start it up again, it should discover that file and apply the rules.

    jmazzeo said

    OK, jscher2000. I followed your instructions in #1 and did get the tabs back below (yay!).
    This response says, ''The following "moving tabs below the URL bar" procedure only works on Linux and Windows. '''It does not work on Mac OS X.''''' ... but see this thread ([/kb/forum-response-tabs-below-url-bar/discuss/7320#post-15861 linked above]) posted by "jmazzeo", a Mac user: https://support.mozilla.org/en-US/questions/1185495 How do I get my tabs back below the bookmark toolbar? And why the hell did you change this??? And now white on black? Unreadable. The instructions by jscher2000 worked for the Mac user in [/questions/1185495] so the following solution should either be added to this response or else this response should link to [/questions/1185495]: ''jscher2000 [/questions/1185495#answer-1030577 said]'' <blockquote> '''(1) Tab bar position''' You can use a custom style rule in a userChrome.css file to rearrange the toolbars. (A) You need to create a new '''chrome''' folder in your profile folder. This article has the steps for that (#1, #2, and optionally #3) https://www.userchrome.org/how-create-userchrome-css.html (B) Download the following file and move it into that chrome folder: https://www.userchrome.org/samples/userChrome-tabs_on_bottom.css (C) Rename the file to just '''userChrome.css''' The next time you quit Firefox and start it up again, it should discover that file and apply the rules. </blockquote> ''jmazzeo [/questions/1185495#answer-1031449 said]'' <blockquote> OK, jscher2000. I followed your instructions in #1 and did get the tabs back below (yay!). </blockquote>
  5. AliceWyman 5146 posts
    Report Abuse

    I checked common forum responses and a revision is pending to add this response. I don't want to approve it without at least adding a link to /questions/1185495 for Mac users.

    I checked [[common forum responses]] and a revision is pending to add this response. I don't want to approve it without at least adding a link to [/questions/1185495] for Mac users.
  6. AliceWyman 5146 posts
    Report Abuse

    I made a revision to this response to include a Mac solution as a hidden comment and approved it (with a note to Rachel). I also approved adding this response to common forum responses.

    I made a revision to this response to include a Mac solution as a hidden comment and approved it (with a note to Rachel). I also approved adding this response to [[common forum responses]].
  7. AliceWyman 5146 posts
    Report Abuse

    I'm not sure why about:profiles instructions were used for this response (I would have used about:support -> Application Basics -> Profile Folder instructions [*]) but, I made another edit that's pending review, to clarify that you have to use the Open ... button next to Root Directory to open the profile in use.

    [*] Related discussion: https://support.mozilla.org/en-US/kb/templateopenprofilefolder/discuss/7231 Update for Firefox 56 Tonnes said

    Spotted the missing Linux entry too and added that. Additionally, the 56+ content does not mention which of the 2 available buttons to click, i.e. the (top) one for the actual profile folder mentioning Roaming, not the bottom one for the local cache folder. Needless to say, I do think it’s important to add that. <snip>

    AliceWyman said

    <snip> As far as this template, I think it would be best to leave it as is, with the old instructions. Using the about:profiles page is too complicated, in my opinion, since it's easy to choose the wrong folder to open. The Root Directory (AppData\Roaming) of the profile in use is the folder that needs to be opened. The Local Directory (AppData\Local) stores the cache, as Tonnes mentioned.
    I'm not sure why about:profiles instructions were used for this response (I would have used about:support -> Application Basics -> Profile Folder instructions [*]) but, I made another edit that's pending review, to clarify that you have to use the Open ... button next to '''Root Directory''' to open the profile in use. [*] Related discussion: https://support.mozilla.org/en-US/kb/templateopenprofilefolder/discuss/7231 Update for Firefox 56 ''Tonnes [[#post-15585|said]]'' <blockquote> Spotted the missing Linux entry too and added that. Additionally, the 56+ content does not mention ''which'' of the 2 available buttons to click, i.e. the (top) one for the actual profile folder mentioning ''Roaming'', not the bottom one for the local cache folder. Needless to say, I do think it’s important to add that. <snip> </blockquote> ''AliceWyman [[#post-15599|said]]'' <blockquote><snip> As far as this template, I think it would be best to leave it as is, with the old instructions. Using the about:profiles page is too complicated, in my opinion, since it's easy to choose the wrong folder to open. The Root Directory (AppData\Roaming) of the profile in use is the folder that needs to be opened. The Local Directory (AppData\Local) stores the cache, as Tonnes mentioned. </blockquote>
    Modified by AliceWyman on
  8. Tonnes 63 posts
    Report Abuse

    Note that note and warning markup does not work in forum responses. Also, the numbering looks a bit odd, so some additional changes may be needed.

    Note that note and warning markup does not work in forum responses. Also, the numbering looks a bit odd, so some additional changes may be needed.
  9. AliceWyman 5146 posts
    Report Abuse

    Tonnes said

    Note that note and warning markup does not work in forum responses. Also, the numbering looks a bit odd, so some additional changes may be needed.

    I made a new revision that's pending review.

    ''Tonnes [[#post-15887|said]]'' <blockquote> Note that note and warning markup does not work in forum responses. Also, the numbering looks a bit odd, so some additional changes may be needed. </blockquote> I made a new revision that's pending review.
  10. Tonnes 63 posts
    Report Abuse

    Thanks. One question: what is so different in the Mac content? Other than for how to access the profile folder, the instructions seem to be similar for that and other OSes (they point to the same code and file), or I’m overlooking something.

    Thanks. One question: what is so different in the Mac content? Other than for how to access the profile folder, the instructions seem to be similar for that and other OSes (they point to the same code and file), or I’m overlooking something.
  11. AliceWyman 5146 posts
    Report Abuse

    Tonnes said

    Thanks. One question: what is so different in the Mac content? Other than for how to access the profile folder, the instructions seem to be similar for that and other OSes (they point to the same code and file), or I’m overlooking something.

    The main difference is that the Mac solution has the person downloading https://www.userchrome.org/samples/userChrome-tabs_on_bottom.css and placing it in the chrome folder, then renaming the file to userChrome.css . That method seems to have less room for error compared to copying the css code from https://www.userchrome.org/what-is-userchrome-css.html#movetabbar and then pasting it into a blank userChrome.css file.

    Here is the content of the downloaded file: oops. forgot the nowiki /* Tab bar below Navigation & Bookmarks Toolbars For best results, show Title Bar or Menu Bar */ #nav-bar { /* main toolbar */ -moz-box-ordinal-group: 1 !important; border-top-width: 0 !important; } #PersonalToolbar { /* bookmarks toolbar */ -moz-box-ordinal-group: 2 !important; } #TabsToolbar { /* tab bar */ -moz-box-ordinal-group: 3 !important; }

    It's exactly the same as what's shown at https://www.userchrome.org/what-is-userchrome-css.html#movetabbar so I suspect it didn't work for Roland (or whichever Mac user tested it) due to user error.

    I think we should remove the Mac warning and edit this canned response to add the download/rename instructions that jscher2000 gave as an alternate method. What do you think?

    ''Tonnes [[#post-15889|said]]'' <blockquote> Thanks. One question: what is so different in the Mac content? Other than for how to access the profile folder, the instructions seem to be similar for that and other OSes (they point to the same code and file), or I’m overlooking something. </blockquote> The main difference is that the Mac solution has the person downloading https://www.userchrome.org/samples/userChrome-tabs_on_bottom.css and placing it in the chrome folder, then renaming the file to userChrome.css . That method seems to have less room for error compared to copying the css code from https://www.userchrome.org/what-is-userchrome-css.html#movetabbar and then pasting it into a blank userChrome.css file. Here is the content of the downloaded file: <sub> oops. forgot the nowiki</sub> <code><nowiki> /* Tab bar below Navigation & Bookmarks Toolbars For best results, show Title Bar or Menu Bar */ #nav-bar { /* main toolbar */ -moz-box-ordinal-group: 1 !important; border-top-width: 0 !important; } #PersonalToolbar { /* bookmarks toolbar */ -moz-box-ordinal-group: 2 !important; } #TabsToolbar { /* tab bar */ -moz-box-ordinal-group: 3 !important; } </nowiki></code> It's exactly the same as what's shown at https://www.userchrome.org/what-is-userchrome-css.html#movetabbar so I suspect it didn't work for Roland (or whichever Mac user tested it) due to user error. I think we should remove the Mac warning and edit this canned response to add the download/rename instructions that jscher2000 gave as an alternate method. What do you think?
    Modified by AliceWyman on
  12. Tonnes 63 posts
    Report Abuse

    That’s the point (no need to copy all of the above), it’s the same code, so basically the instructions for downloading the file instead can be similar for all OSes, can’t they?

    Btw, can you take a look here?

    That’s the point (no need to copy all of the above), it’s the same code, so basically the instructions for downloading the file instead can be similar for all OSes, can’t they? Btw, can you take a look [https://support.mozilla.org/en-US/kb/forum-response-legacy-add-ons-webextensions/discuss/7311#post-15876 here]?
  13. AliceWyman 5146 posts
    Report Abuse

    Yes, the instructions can be the same of all OS's. I added the instructions from jscher2000 as an alternative solution, in a new revision. I don't want to step on anyone's toes (Joni wrote the original response and Roland added the Mac warning) but if you think we only need one set of instructions, can we agree on which to use?

    Yes, the instructions can be the same of all OS's. I added the instructions from jscher2000 as an alternative solution, in a new revision. I don't want to step on anyone's toes (Joni wrote the original response and Roland added the Mac warning) but if you think we only need one set of instructions, can we agree on which to use?
  14. AliceWyman 5146 posts
    Report Abuse

    I made another revision to change instructions to open the profile frolder from about:profiles to about:support along with some other edits. I'll go ahead and approve this last edit if there are no objections.

    I made another revision to change instructions to open the profile frolder from about:profiles to about:support along with some other edits. I'll go ahead and approve this last edit if there are no objections.
  15. Roland Tanglao 336 posts
    Report Abuse

    I tested on OS 10.11.6 and it didn't work, so it was my user error :-) Haha wouldn't be the first time!

    On the same Mac it now works with the November 19, 2017 revision.

    I did have to uncomment the following rule in order not to obscure the back button. Please see (screenshot of obscured back button, Mac OS X 10.11.6, Firefox 57)

    #navigator-toolbox { padding-top: 20px !important; }

    Cheers!

    ...Roland

    I tested on OS 10.11.6 and it didn't work, so it was my user error :-) Haha wouldn't be the first time! On the same Mac it now works with the November 19, 2017 revision. I did have to uncomment the following rule in order not to obscure the back button. Please see ([https://flic.kr/p/21JpMSR screenshot of obscured back button, Mac OS X 10.11.6, Firefox 57]) <blockquote> <nowiki> #navigator-toolbox { padding-top: 20px !important; } </nowiki> </blockquote> Cheers! ...Roland
    Modified by Roland Tanglao on
  16. AliceWyman 5146 posts
    Report Abuse

    Roland, Thanks for your post.

    For the record, jscher2000 updated his https://www.userchrome.org/what-is-userchrome-css.html page on Nov 19, 2017 and changed the code in the "Move the Tab Bar Below the Other Toolbars" example here and in the linked userChrome-tabs_on_bottom.css file. Both now include the following code: /* Tab bar below Navigation & Bookmarks Toolbars */ #nav-bar { /* main toolbar */ -moz-box-ordinal-group: 1 !important; } #PersonalToolbar { /* bookmarks toolbar */ -moz-box-ordinal-group: 2 !important; } #TabsToolbar { /* tab bar */ -moz-box-ordinal-group: 3 !important; } /* To create space for the standard window buttons, either (1) Show the title bar (2) On Windows, show the menu bar (3) Enable the following rule by removing the comment tags */ /* #navigator-toolbox { padding-top: 20px !important; } */ /* If there is an undesirable color behind the tab bar, either (1) Install a theme to fill in the background from https://addons.mozilla.org/firefox/themes/ (2) Enable the following rule by removing the comment tags, then edit to the desired color */ /* #TabsToolbar { background-color: #f8f8f8 !important; } */

    About the Alternative solution section I added: The main reason I added it is because it's easier to download a .css file, place it in the chrome folder and then rename it, compared to manually creating a userChrome.css file and copy/pasting the content, IF the only css code is to modify the tabs placement. We should add the same "Tip" that's under the original instructions, Tip: Turn on your title bar or menu bar after you've made these changes. ...and maybe link to the Customize Firefox controls, buttons and toolbars article. I'll make that edit.

    We could also consolidate the two sets of instructions. I'll leave that up to others. If anyone sees something else in my last revision that needs updating, please make the edit.

    Roland, Thanks for your post. For the record, jscher2000 updated his https://www.userchrome.org/what-is-userchrome-css.html page on Nov 19, 2017 and changed the code in the "Move the Tab Bar Below the Other Toolbars" example [https://www.userchrome.org/what-is-userchrome-css.html#movetabbar here] and in the linked userChrome-tabs_on_bottom.css file. Both now include the following code: <code><nowiki> /* Tab bar below Navigation & Bookmarks Toolbars */ #nav-bar { /* main toolbar */ -moz-box-ordinal-group: 1 !important; } #PersonalToolbar { /* bookmarks toolbar */ -moz-box-ordinal-group: 2 !important; } #TabsToolbar { /* tab bar */ -moz-box-ordinal-group: 3 !important; } /* To create space for the standard window buttons, either (1) Show the title bar (2) On Windows, show the menu bar (3) Enable the following rule by removing the comment tags */ /* #navigator-toolbox { padding-top: 20px !important; } */ /* If there is an undesirable color behind the tab bar, either (1) Install a theme to fill in the background from https://addons.mozilla.org/firefox/themes/ (2) Enable the following rule by removing the comment tags, then edit to the desired color */ /* #TabsToolbar { background-color: #f8f8f8 !important; } */ </nowiki></code> About the '''Alternative solution''' section I added: The main reason I added it is because it's easier to download a .css file, place it in the chrome folder and then rename it, compared to manually creating a userChrome.css file and copy/pasting the content, IF the only css code is to modify the tabs placement. We should add the same "Tip" that's under the original instructions, '''''Tip:''' Turn on your title bar or menu bar after you've made these changes.'' ...and maybe link to the [[Customize Firefox controls, buttons and toolbars]] article. I'll make that edit. We could also consolidate the two sets of instructions. I'll leave that up to others. If anyone sees something else in my last revision that needs updating, please make the edit.
  17. Tonnes 63 posts
    Report Abuse

    I still see no point in writing duplicate sections, so would prefer to limit it to mentioning the file method only if there should be only one. An additional note about the ability to copy text instead would still be useful though, and only because of the fact there may already be an userChrome.css file, so the user needs to copy and paste (add) that text to the existing file.

    Nit: instead of "close the file and save your changes", I’d use "save your changes and close the file" for obvious reasons. ;)

    I still see no point in writing duplicate sections, so would prefer to limit it to mentioning the file method only if there should be only one. An additional note about the ability to copy text instead would still be useful though, and only because of the fact there may ''already be'' an userChrome.css file, so the user ''needs to'' copy and paste (add) that text to the existing file. Nit: instead of "close the file and save your changes", I’d use "save your changes and close the file" for obvious reasons. ;)
  18. AliceWyman 5146 posts
    Report Abuse

    Tonnes said

    Nit: instead of "close the file and save your changes", I’d use "save your changes and close the file" for obvious reasons. ;)

    On Windows, when you first create or edit a file and then close Notepad (the Text Document editor included with Windows), you are prompted to save your changes .... but I see your point.

    I'll let you or others to make future changes but I think we should probably keep both solutions and let the person using the forum response decide. The Alternative solution is lots easier for those users who don't know how to create a text file with Notepad using the All Files (*.*) drop-down option or how to set Windows to view all file extensions. I was trying to find a Microsoft article but the best I could find was this one for Windows 8 and below: https://blogs.technet.microsoft.com/activedirectoryua/2013/05/22/how-to-see-those-file-extensions-in-windows/

    ''Tonnes [[#post-15903|said]]'' <blockquote> Nit: instead of "close the file and save your changes", I’d use "save your changes and close the file" for obvious reasons. ;) </blockquote> On Windows, when you first create or edit a file and then close Notepad (the Text Document editor included with Windows), you are prompted to save your changes .... but I see your point. I'll let you or others to make future changes but I think we should probably keep both solutions and let the person using the forum response decide. The '''Alternative solution''' is lots easier for those users who don't know how to create a text file with Notepad using the All Files (*.*) drop-down option or how to set Windows to view all file extensions. I was trying to find a Microsoft article but the best I could find was this one for Windows 8 and below: https://blogs.technet.microsoft.com/activedirectoryua/2013/05/22/how-to-see-those-file-extensions-in-windows/
  19. Tonnes 63 posts
    Report Abuse

    We should not overdo this, of course. The response is intended both for users who are not familiar with a userChrome.css file, and ones who already have it. So yes, downloading a file is much easier and I prefer it, but that may cause a question if it already exists. Therefor including a short and easy reference to the page that shows the code itself would suffice IMO, or ask the user to open both files in an editor and copy the downloaded file’s content into the existing file. Or the response should contain 2 sections, one for the scenario where the file does not exist, and one for when it does.

    I think things like hidden file extensions are basics and should not be new, but if it comes in handy, this link may do. Funny to see it’s hard to find a working URL for Windows 8 and up...

    A point of worry for Mac users perhaps: at the time of renaming the button label for Windows (from "Show folder" to "Open folder", see bug 1300562 and 1309297), I wondered where Mac users actually land. I do recall asking around and being told it was the parent folder, as opposed to Windows and Linux. I just did again on IRC and was told they actually do land in /Profiles and with the active profile selected (I’m not sure if the latter is always true, perhaps it remembers the last selected one), so users may need to step into that folder first in order not to create the chrome folder in the /Profiles folder instead. This seems to be confirmed by this question.

    We should not overdo this, of course. The response is intended both for users who are not familiar with a userChrome.css file, and ones who already have it. So yes, downloading a file is much easier and I prefer it, but that may cause a question if it already exists. Therefor including a short and easy reference to the page that shows the code itself would suffice IMO, or ask the user to open both files in an editor and copy the downloaded file’s content into the existing file. Or the response should contain 2 sections, one for the scenario where the file does not exist, and one for when it does. I think things like hidden file extensions are basics and should not be new, but if it comes in handy, [https://support.microsoft.com/en-us/help/865219/how-to-show-or-hide-file-name-extensions-in-windows-explorer this link] may do. Funny to see it’s hard to find a working URL for Windows 8 and up... A point of worry for '''Mac users''' perhaps: at the time of renaming the button label for Windows (from "Show folder" to "Open folder", see [https://bugzilla.mozilla.org/show_bug.cgi?id=1300562#c0 bug 1300562] and 1309297), I wondered where Mac users actually land. I do recall asking around and being told it was the parent folder, as opposed to Windows and Linux. I just did again on IRC and was told they actually do '''land in /Profiles''' and with the active profile selected (I’m not sure if the latter is always true, perhaps it remembers the last selected one), so users may need to step into that folder first in order not to create the chrome folder in the /Profiles folder instead. This seems to be confirmed by [/questions/1189136 this question].
  20. AliceWyman 5146 posts
    Report Abuse

    You're right, Tonnes. On Mac, the "Show in Finder" button opens the Profiles folder that contains the <random>.default and other profile folders. We should make that clearer for Mac users.

    I updated the article and approved it. I'll wait awhile to see if there is anything else, before marking it RFL.

    You're right, Tonnes. On Mac, the "Show in Finder" button opens the '''Profiles''' folder that <u>contains</u> the <random>.default and other profile folders. We should make that clearer for Mac users. I updated the article and approved it. I'll wait awhile to see if there is anything else, before marking it RFL.
    Modified by AliceWyman on
  1. 1
  2. 2