Firefox tab "close" button to appear when you hover over a tab?


Recommended Posts

I am trying to find a Firefox add-on/extension or hack that will enable or make a Firefox tab "close" button (x) appear when you hover over an inactive tab (all tabs except the currently viewed (active) tab) so that one doesn't have to click on the tab and then click the close button. In the case of Chrome, the tab close buttons are always visible on all tabs, but the close button doesn't light up until the mouse cursor is over the close button. In the case of IE8 and IE9, you don't even see the tab close buttons on inactive tabs until you hover over an inactive tab with the mouse cursor. When you do hover over an inactive tab, the close button appears and if you hover over the close button, then the tab close button lights up (like Chrome).

I should point out that I prefer the IE8/IE9 functionality where I don't even see the tab close buttons until I hover over an inactive tab. I think I can get what I'm looking for with Tab Mix Plus, but I don't want all the "stuff" and bloat that it brings. I would think what I'm looking for is either already out there or could be developed in a tiny little tweak/hack/add-on.

I'm familiar with the Firefox "browser.tabs.closeButtons" preference (http://kb.mozillazine.org/Browser.tabs.closeButtons), but that doesn't seem to help.

Any help would be greatly appreciated.

Which version of Firefox are you using? As far as I'm aware, the tabs in Firefox 4 behave the same way as the tabs in Chrome 10. The only difference is the colour of the "x" button when you hover your cursor over it.

501521885.png

552178835.png

I am using Firefox 4.0 and I do NOT have that functionality. So, I'm guessing that maybe one of my add-ons is messing with Firefox's default functionality. I'll look into it. Thanks, Anaron.

I am using a couple of non-default profiles for testing since my default profile is still linked to Firefox 3.6.16. I wonder if that has anything to do with it? I would think it is a add-on conflict or something along those lines.

That's odd. I took the screenshots with a default installation of Firefox 4 (that was installed over Firefox 3.6). I am, however, using a new profile. As for my settings, the only things I changed related to hardware acceleration. You can restart Firefox 4 with add-ons disabled. Just click on the Firefox button and hover your cursor over "Help". From there, you should see "Restart Firefox with Add-ons Disabled".

Question for Anaron or anyone else...

I currently have 39 tabs open in Firefox 4 so I can't easily test this without saving my session or closing tabs. I just want to make sure of something. The close tab buttons like Anaron showed do still appear when you open many more tabs, correct? In my current case, the tab width of each tab is probably about half (maybe even a little less) than what he is showing in his Firefox 4 pictures because I have so many tabs open.

That's interesting. I've never had that many tabs open before. Anyway, I just opened a bunch of tabs and noticed that the "x" button disappears after opening an 11th tab. This is with Firefox 4 at fullscreen (1680x1050). I assume the point at which the "x" button disappears varies with resolution. Chrome 10 acts the same way but with a slight difference. Instead of the button disappearing after opening an 11th tab, it disappears after opening tab #25.

  On 27/03/2011 at 01:51, Anaron said:

That's odd. I took the screenshots with a default installation of Firefox 4 (that was installed over Firefox 3.6). I am, however, using a new profile. As for my settings, the only things I changed related to hardware acceleration. You can restart Firefox 4 with add-ons disabled. Just click on the Firefox button and hover your cursor over "Help". From there, you should see "Restart Firefox with Add-ons Disabled".

I restarted Firefox in Safe-Mode (Add-ons disabled) and it didn't change anything. As mentioned in my previous post, I wonder if Firefox 4 is really like Chrome or IE8/IE9 even when many tabs are open and the tab widths are a lot smaller. I need to test that to make sure.

  On 27/03/2011 at 01:53, fr33k said:

Thanks for the help fr33k, but I don't want the size/bloat and everything else that comes with Tab Mix Plus for something so simple. If needed, I'll make a tiny little add-on for this myself. It would be nice if that wasn't necessary, but it might be.

  On 27/03/2011 at 02:02, Anaron said:

That's interesting. I've never had that many tabs open before. Anyway, I just opened a bunch of tabs and noticed that the "x" button disappears after opening an 11th tab. This is with Firefox 4 at fullscreen (1680x1050). I assume the point at which the "x" button disappears varies with resolution. Chrome 10 acts the same way but with a slight difference. Instead of the button disappearing after opening an 11th tab, it disappears after opening tab #25.

I didn't test that far with Chrome 10 or IE 9. Thanks for the feedback.

You can control the point when the close button disappears with browser.tabs.tabClipWidth setting in about:config.

The setting is used to set the point where the close button disappears, e.g. setting it to 50 pixels will keep close button on background tabs until the tabs are shorter than 50 pixels (which should never happen) effectively forcing the close buttons to appear always.

  On 27/03/2011 at 04:18, Anaron said:

Can you see the close button with two tabs open? If so, then your issue is with the number of tabs open.

Yes. I saved my session of tabs and got Firefox down to just a few tabs and I see the tab close buttons on all tabs.

  On 27/03/2011 at 04:26, macel said:

You can control the point when the close button disappears with browser.tabs.tabClipWidth setting in about:config.

The setting is used to set the point where the close button disappears, e.g. setting it to 50 pixels will keep close button on background tabs until the tabs are shorter than 50 pixels (which should never happen) effectively forcing the close buttons to appear always.

Thank you very much, macel. I think this is as simple and tiny a solution as I am going to find or could even create. It works beautifully. I still would prefer the IE8/IE9 functionality where tab close buttons don't appear until you hover over an inactive/background tab, but I will be thankful and count my blessings.

Here is the scoop or summary of what I found:

In testing on my install of Firefox 4.0 on Windows 7 x64,

For 1-14 tabs, the tab width varies between a max of 250 pixels and about 108 or 109 pixels.

For 15 or more tabs, the tab width is 100 pixels.

So, I entered "about:config" into the address bar to change the Firefox "browser.tabs.tabClipWidth" preference. (see http://kb.mozillazine.org/browser.tabs.tabClipWidth for more info.) For those not clear, once you enter about:config and are in the advanced settings area, just paste in browser.tabs.tabClipWidth to filter that result or scroll down to it. The default setting is 140. 0 (zero) is an invalid entry. Since the minimum tab width is 100 pixels, 99 or less makes the tab close buttons always appear and useable no matter what.

100 or greater = tab close buttons do not appear until you click on an inactive/background tab (see the mozillazine link above for exceptions or issues with this)

1-99 = tab close buttons appear always on both the active/foreground tab and inactive/background tabs and are useable WITHOUT first having to click on an inactive/background tab

Since 96 is a nice number that 2, 8, 16, 32, etc goes into, I used 96 for the preference. It doesn't matter I suppose. The bottom line is the tab close button always appears on all tabs and you can close an inactive/background tab without having to first click on it to see the tab close button.

Thanks to macel, Anaron, and fr33k for the interest and help! ;)

I'm editing this post to add a caveat. If one uses the "browser.tabs.tabMinWidth" preference (removed from Firefox 4.0, but see http://kb.mozillazine.org/browser.tabs.tabMinWidth for more info) or Custom Tab Width add-on/extension (https://addons.mozilla.org/en-US/firefox/addon/custom-tab-width/) to change the minimum tab width, then obviously the preference changed mentioned above that worked for me will not work necessarily and/or will have to be modified.

  On 27/03/2011 at 16:14, JayZJay said:

I still would prefer the IE8/IE9 functionality where tab close buttons don't appear until you hover over an inactive/background tab

This is pretty easy to do with some CSS styling. Here, paste this bit of text into either userchrome.css (in your profile folder), or use the Stylish extension:

.tabbrowser-tab:not([selected]) .tab-close-button {
	visibility: hidden !important;
	margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
	visibility: visible !important;	
	margin-left: 0px !important;
}

  • Like 3
  On 28/03/2011 at 00:16, Hitchhiker427 said:

This is pretty easy to do with some CSS styling. Here, paste this bit of text into either userchrome.css (in your profile folder), or use the Stylish extension:

.tabbrowser-tab:not([selected]) .tab-close-button {
	visibility: hidden !important;
	margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
	visibility: visible !important;	
	margin-left: 0px !important;
}

Thanks. I had seen solutions involving the Stylish extension, but nothing for sure that involved just modifying the userchrome.css file. I'll check out the code.

  On 28/03/2011 at 00:16, Hitchhiker427 said:

This is pretty easy to do with some CSS styling. Here, paste this bit of text into either userchrome.css (in your profile folder), or use the Stylish extension:

.tabbrowser-tab:not([selected]) .tab-close-button {
	visibility: hidden !important;
	margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
	visibility: visible !important;	
	margin-left: 0px !important;
}

CSS code works like a charm and gives you functionality just like how IE8/IE9 handles the tab close buttons, with the exception that the tab close buttons in Firefox do not light up red or anything like that. Hitchhiker, could you easily add that?

  On 29/03/2011 at 20:29, JayZJay said:

CSS code works like a charm and gives you functionality just like how IE8/IE9 handles the tab close buttons, with the exception that the tab close buttons in Firefox do not light up red or anything like that. Hitchhiker, could you easily add that?

I'm not exactly sure what you mean. If you're looking for red close buttons, you can try the Windows 7 style close buttons that I use for my tabs:

.tab-close-button {
  list-style-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAQCAYAAABQrvyxAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAZdEVYdFNvZnR3YXJlAFBhaW50Lk5FVCB2My41Ljg3O4BdAAAERElEQVRIS9WWa1BUZRzG16/6pWbKvpdGmjPVUDPUaGp+MChtGyawi4xjQd7xA0oMSoASMZKyAROXYBAEAxovC5Fc5bJDkOumQKEBIsvusiZpSTMi7M7T+5zdc3rPjm071pfOzDP/9/0/v2f3/e85MMdgXBZh3LxqA9Y98njIIs+cQVxi/UB55v6LvOGNJ19AS0kp/hi0hizyzPEArB2V1fA6rocs8nK+zmTCcPe3GPuuDRMXOjFp7YLD1g3nD91K5Z59+uTIq3kDf/mZy9/jRu2XIYs8cxyA1TsxBk/f+ZBFXs4PtJlxJjsJraYDsBRnorc0C/3l2bBW5CiVe/bpkyOv5pUD3LH1YaqmGO6TfnEtpPVUz98nrxvg2hV4LC3w9AiJOq+o2ddT+37PI/pewcv5yy2ncerQHpzL3Y/Oz1PRU5iG3qJ09JeKYUTlnn365MjrBvjtggWuykJFqVu2IDomQVHgmr5TiLxugKuD8LSbMd/egMM7d2t5/XoXPB1mwTXAK3g5f+nc16hP24amT/ZiR2y0lt/zzlvamn365MjrBrjdJ5658jw4yvKUgHoFrlWGvG6AoYuYb6pTFCyvMl7By3lbYy1qk7eiIX170Dx9cuR1A/xqaYe96Agmio8gZfN7ug/hMDwU+3bhkyEvH8Bj68Xc6eOYO3Uch+N9d0++uD+UkKD480Lk5bz1TDVq9r6LsylbkWB8/b559umTI68b4GrJUbRGhqMlKhytQttXRmgfwi/nnr4q8vIBpnKSMfTsIgw9swg/CiU9F6bLc+/zF4q6EOTlvDljP5IeNSB1sQEHHzPgzbAndHnu2adPjrxugJ/LTDgf/bKinWtWKuHR0VFN3LOvMuQDBxheuxjUvogV982zf8XPBBvA6D984Pez/7cDjFUVwRIXhZ6413RfLg/CNRmKvDyA23QQI7FLMRKzJGh+JEYwgiOvuwPijiQtWYDUsAVB8/TJmaU7qPwbvV5fgf4dsUKbkBi5XvvLD1zTp8jLB7hZ+SnGd4cLPY+PonyPHxW4pj++Kxzk5XxzQRrSX3wI2aseRkzEci3/9kt/rdmnT4687hFyNNbDtu+Df1C85pOXD3CrsRD2zFcwKWTPXKtoMkOV6Gew7/MnhUdeznefyIFp01KUxD2FiveXoSp+OWo+fBpfbVuhVO7Zp0+OvG4Ad/s3GPg4EQNpiRgUdVBUrpV9QGWPvHyAGesJOPM3wFWwUaob4WIvn1WIXoGPIS/nLzZ9gZMHVuNs1jo0565H29FX0ZEXia78KKVyzz59cuS1AcRLGdrEu810b2fIIs8cXyVYu2oLcNdhxl1nPWZdFZh15+PeL1mYm07BvRvHMDtVLrw6HyNEXs43lH2G8Us1cA1XYXq8FLftx3DHlYkZdzJ+d+Ti1kQJbl6rhvOnOoUjr+Z5ACNfjDhRqCIvv40+SF5+G/03ef6I/+vrT4dImkwPzI8yAAAAAElFTkSuQmCC") !important;
}

.tab-close-button:not([selected]) {
  -moz-image-region: rect(0, 16px, 16px, 0) !important;
}

.tab-close-button:hover,
.tab-close-button:hover[selected="true"] {
  -moz-image-region: rect(0, 32px, 16px, 16px) !important;
}

.tab-close-button:hover:active,
.tab-close-button:hover:active[selected="true"] {
  -moz-image-region: rect(0, 48px, 16px, 32px) !important;
}

.tabbrowser-tab:not([selected]) .tab-close-button {
        visibility: hidden !important;
        margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
        visibility: visible !important; 
        margin-left: 0px !important;
}

If you're looking for something exactly like IE9 (gray 'x' that turns red when hovering), here (I just changed the embedded image):

.tab-close-button {
  list-style-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAQCAYAAABQrvyxAAAABGdBTUEAALGPC/xhBQAAAAlwSFlzAAAOwgAADsIBFShKgAAAABl0RVh0U29mdHdhcmUAUGFpbnQuTkVUIHYzLjUuODc7gF0AAAG4SURBVEhL7VM7TsNAEPUBOA5J4CKEQAGCvQNU3AKIAzTBSZBDAaIzHAQRY/xZO074CS4w7Fuwsw0aFzRItjSap/f8xjOza8uqn3oDf7cBz7ul8fiS8tlcFFWBwXneHXFfyg8OKN3YpDeZlf53hcFB4/zTnV1KWi36lGnpBwYHjfNbrjums5NTQp7mM4EwOa4AGpWrq3qI10QKhMlxfjQaLS3pIT6UF2FynN+S6VQ17FLP7qkhXB0FhsYVmIeRkJ0NSlZWCNnE0Dj/WxSLuNnUQyCbGBrn17pMMzEaXZDdtXUAV2m+vHJBKJKfIYpB8qew2sdVkVc1aLH14jTAVWoeL8VJKobDEdnHXR3A4KoWyPUAHYrVKSCAwVX1v6hhi80XJwGukj+MEzEYDKmrGkde4BFB44pkfiCS9e/mkU0MjfPPg6dfr9Cz0ji/5TgDOjo8JuQgjAVCc0ffHFcgbq9T3FKbV1lOfIEwOdZv3P/ZYyAQ5n/A+a2r6xvq9x2aPC6OzFe4f+4QNK5AtLdP4VqbovuHclvAmlMa50+2tilablD24Jf+qVpC1GiQVBrnr/V6A/UG/uEGvgBxw8Y81yU7fAAAAABJRU5ErkJggg==") !important;
}

.tab-close-button:not([selected]) {
  -moz-image-region: rect(0, 16px, 16px, 0) !important;
}

.tab-close-button:hover,
.tab-close-button:hover[selected="true"] {
  -moz-image-region: rect(0, 32px, 16px, 16px) !important;
}

.tab-close-button:hover:active,
.tab-close-button:hover:active[selected="true"] {
  -moz-image-region: rect(0, 48px, 16px, 32px) !important;
}

.tabbrowser-tab:not([selected]) .tab-close-button {
        visibility: hidden !important;
        margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
        visibility: visible !important; 
        margin-left: 0px !important;
}

  On 28/03/2011 at 00:16, Hitchhiker427 said:

This is pretty easy to do with some CSS styling. Here, paste this bit of text into either userchrome.css (in your profile folder), or use the Stylish extension:

.tabbrowser-tab:not([selected]) .tab-close-button {
	visibility: hidden !important;
	margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
	visibility: visible !important;	
	margin-left: 0px !important;
}

Works great (Y)

  On 30/03/2011 at 16:41, Daybreak said:

As an aside, why not just middle click to close? Vastly more simple than tweaking around with Firefox.

I use Logitech mice with a micro-gear/ratchet middle button that switches between smooth, hyper-fast scrolling and the common click-to-click/notched scrolling. These don't have middle-clicking, which is fine for me since I never middle-clicked anyway. Middle-clicking on these switches the scrolling of the the wheel, literally changing gears or ratchets. I love the mice, but the bottom line is what you suggest isn't an option.

  On 30/03/2011 at 04:25, Hitchhiker427 said:

I'm not exactly sure what you mean. If you're looking for red close buttons, you can try the Windows 7 style close buttons that I use for my tabs:

.tab-close-button {
  list-style-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAQCAYAAABQrvyxAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAZdEVYdFNvZnR3YXJlAFBhaW50Lk5FVCB2My41Ljg3O4BdAAAERElEQVRIS9WWa1BUZRzG16/6pWbKvpdGmjPVUDPUaGp+MChtGyawi4xjQd7xA0oMSoASMZKyAROXYBAEAxovC5Fc5bJDkOumQKEBIsvusiZpSTMi7M7T+5zdc3rPjm071pfOzDP/9/0/v2f3/e85MMdgXBZh3LxqA9Y98njIIs+cQVxi/UB55v6LvOGNJ19AS0kp/hi0hizyzPEArB2V1fA6rocs8nK+zmTCcPe3GPuuDRMXOjFp7YLD1g3nD91K5Z59+uTIq3kDf/mZy9/jRu2XIYs8cxyA1TsxBk/f+ZBFXs4PtJlxJjsJraYDsBRnorc0C/3l2bBW5CiVe/bpkyOv5pUD3LH1YaqmGO6TfnEtpPVUz98nrxvg2hV4LC3w9AiJOq+o2ddT+37PI/pewcv5yy2ncerQHpzL3Y/Oz1PRU5iG3qJ09JeKYUTlnn365MjrBvjtggWuykJFqVu2IDomQVHgmr5TiLxugKuD8LSbMd/egMM7d2t5/XoXPB1mwTXAK3g5f+nc16hP24amT/ZiR2y0lt/zzlvamn365MjrBrjdJ5658jw4yvKUgHoFrlWGvG6AoYuYb6pTFCyvMl7By3lbYy1qk7eiIX170Dx9cuR1A/xqaYe96Agmio8gZfN7ug/hMDwU+3bhkyEvH8Bj68Xc6eOYO3Uch+N9d0++uD+UkKD480Lk5bz1TDVq9r6LsylbkWB8/b559umTI68b4GrJUbRGhqMlKhytQttXRmgfwi/nnr4q8vIBpnKSMfTsIgw9swg/CiU9F6bLc+/zF4q6EOTlvDljP5IeNSB1sQEHHzPgzbAndHnu2adPjrxugJ/LTDgf/bKinWtWKuHR0VFN3LOvMuQDBxheuxjUvogV982zf8XPBBvA6D984Pez/7cDjFUVwRIXhZ6413RfLg/CNRmKvDyA23QQI7FLMRKzJGh+JEYwgiOvuwPijiQtWYDUsAVB8/TJmaU7qPwbvV5fgf4dsUKbkBi5XvvLD1zTp8jLB7hZ+SnGd4cLPY+PonyPHxW4pj++Kxzk5XxzQRrSX3wI2aseRkzEci3/9kt/rdmnT4687hFyNNbDtu+Df1C85pOXD3CrsRD2zFcwKWTPXKtoMkOV6Gew7/MnhUdeznefyIFp01KUxD2FiveXoSp+OWo+fBpfbVuhVO7Zp0+OvG4Ad/s3GPg4EQNpiRgUdVBUrpV9QGWPvHyAGesJOPM3wFWwUaob4WIvn1WIXoGPIS/nLzZ9gZMHVuNs1jo0565H29FX0ZEXia78KKVyzz59cuS1AcRLGdrEu810b2fIIs8cXyVYu2oLcNdhxl1nPWZdFZh15+PeL1mYm07BvRvHMDtVLrw6HyNEXs43lH2G8Us1cA1XYXq8FLftx3DHlYkZdzJ+d+Ti1kQJbl6rhvOnOoUjr+Z5ACNfjDhRqCIvv40+SF5+G/03ef6I/+vrT4dImkwPzI8yAAAAAElFTkSuQmCC") !important;
}

.tab-close-button:not([selected]) {
  -moz-image-region: rect(0, 16px, 16px, 0) !important;
}

.tab-close-button:hover,
.tab-close-button:hover[selected="true"] {
  -moz-image-region: rect(0, 32px, 16px, 16px) !important;
}

.tab-close-button:hover:active,
.tab-close-button:hover:active[selected="true"] {
  -moz-image-region: rect(0, 48px, 16px, 32px) !important;
}

.tabbrowser-tab:not([selected]) .tab-close-button {
        visibility: hidden !important;
        margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
        visibility: visible !important; 
        margin-left: 0px !important;
}

If you're looking for something exactly like IE9 (gray 'x' that turns red when hovering), here (I just changed the embedded image):

.tab-close-button {
  list-style-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAQCAYAAABQrvyxAAAABGdBTUEAALGPC/xhBQAAAAlwSFlzAAAOwgAADsIBFShKgAAAABl0RVh0U29mdHdhcmUAUGFpbnQuTkVUIHYzLjUuODc7gF0AAAG4SURBVEhL7VM7TsNAEPUBOA5J4CKEQAGCvQNU3AKIAzTBSZBDAaIzHAQRY/xZO074CS4w7Fuwsw0aFzRItjSap/f8xjOza8uqn3oDf7cBz7ul8fiS8tlcFFWBwXneHXFfyg8OKN3YpDeZlf53hcFB4/zTnV1KWi36lGnpBwYHjfNbrjums5NTQp7mM4EwOa4AGpWrq3qI10QKhMlxfjQaLS3pIT6UF2FynN+S6VQ17FLP7qkhXB0FhsYVmIeRkJ0NSlZWCNnE0Dj/WxSLuNnUQyCbGBrn17pMMzEaXZDdtXUAV2m+vHJBKJKfIYpB8qew2sdVkVc1aLH14jTAVWoeL8VJKobDEdnHXR3A4KoWyPUAHYrVKSCAwVX1v6hhi80XJwGukj+MEzEYDKmrGkde4BFB44pkfiCS9e/mkU0MjfPPg6dfr9Cz0ji/5TgDOjo8JuQgjAVCc0ffHFcgbq9T3FKbV1lOfIEwOdZv3P/ZYyAQ5n/A+a2r6xvq9x2aPC6OzFe4f+4QNK5AtLdP4VqbovuHclvAmlMa50+2tilablD24Jf+qVpC1GiQVBrnr/V6A/UG/uEGvgBxw8Y81yU7fAAAAABJRU5ErkJggg==") !important;
}

.tab-close-button:not([selected]) {
  -moz-image-region: rect(0, 16px, 16px, 0) !important;
}

.tab-close-button:hover,
.tab-close-button:hover[selected="true"] {
  -moz-image-region: rect(0, 32px, 16px, 16px) !important;
}

.tab-close-button:hover:active,
.tab-close-button:hover:active[selected="true"] {
  -moz-image-region: rect(0, 48px, 16px, 32px) !important;
}

.tabbrowser-tab:not([selected]) .tab-close-button {
        visibility: hidden !important;
        margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
        visibility: visible !important; 
        margin-left: 0px !important;
}

Thanks for the code, but neither one of these seem to change anything from the first CSS code you posted except for making the tab close buttons appear all the time. That is the only difference I see. The first CSS code you posted was more like IE in that it didn't show the tab close buttons on inactive/background tabs until you hovered over them. Not sure what is wrong with these larger code snippets. It would be cool if tab close buttons would "light" up when you hover over them and I think that is what you are saying these larger code snippets are supposed to do in some fashion. I'm willing to play with this a bit more if you find the problem in these larger code snippets or know what the problem is. Thanks for all the work and help, Hitchhiker...

  On 31/03/2011 at 06:00, Hitchhiker427 said:

Yeah, the base64 was screwed up. Here:

Win7 Close Buttons

IE9 Close Buttons

Yeah, I had a feeling dnast was correct and thought that might be the case when I posted my findings, but wasn't sure. I should have articulated that in my post. Thanks to you as well as dnast for being on top of it. I'll test out the 2 options.

  On 28/03/2011 at 00:16, Hitchhiker427 said:

This is pretty easy to do with some CSS styling. Here, paste this bit of text into either userchrome.css (in your profile folder), or use the Stylish extension:

.tabbrowser-tab:not([selected]) .tab-close-button {
	visibility: hidden !important;
	margin-left: -16px !important;
}

.tabbrowser-tab:not([selected]):hover .tab-close-button {
	visibility: visible !important;	
	margin-left: 0px !important;
}

  On 29/03/2011 at 20:29, JayZJay said:

CSS code works like a charm and gives you functionality just like how IE8/IE9 handles the tab close buttons, with the exception that the tab close buttons in Firefox do not light up red or anything like that. Hitchhiker, could you easily add that?

In working with a different profile, I just realized that you have to use this code in addition to changing the Firefox preference "browser.tabs.tabClipWidth" to a value less than 100 if you want the functionality of having tab close buttons that do not appear on inactive/background tabs unless you hover over them. I had already changed this preference before and as a result, when I created a userChrome.css file and added this code, it worked as I intended. But, when creating a userChrome.css file with this code for another Firefox profile where I had NOT changed the "browser.tabs.tabClipWidth" preference, the results were not the same and I realized that you have to use the preference change along with the userChrome.css file.

I hope that makes sense to those that care...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • It funny how in a few short years Intel has become the budget brand. I just had to do an unexpected platform swap on my main system due to memory stability issues that suddenly developed. I went with a 9800X3D, but seeing these prices making me regret not at least considering this direction. I really don't need top-tier performance, and between a cheaper CPU and cheaper board, the Intel option looks like it would have been $300-400 cheaper. I already have a 360 AIO, so the extra heat wouldn't have been a big deal. Oh well, live and learn. I normally am the kind of person that will consider something like this for weeks, but I needed to move quickly and my decision point was "9800X3D is a fantastic chip, and Ultra-200 is basically a joke" which is true, but what I didn't consider is a CPU like this 265K is still worlds head of my 5800X, and I really don't need more than that. Its just the enthusiast mindset :-)
    • The only compelling reason for 99% of people will be Windows 10's end-of-support on October, nothing more.
    • This thread has run its course. The complaint has been noted and we'll handle things on our side.  Again, for future reference please report a post that you have an issue with and we will investigate.  <Thread closed>
    • AMD Ryzen 9000, 8000, 7000 CPUs have a vulnerable TPM-Pluton, major firmware fix released by Sayan Sen Last week, the Trusted Computing Group (TCG), which is the developer of the Trusted Platform Module (TPM) security standard, alerted the press and AMD about a new TPM vulnerability on Ryzen processors. Tracked under ID "CVE-2025-2884" (AMD is tracking it as "AMD-SB-4011"), the vulnerability allows an attacker to exploit the vulnerability by sending malicious commands to read data stored in the TPM via an information disclosure flaw or potentially impact TPM availability on systems through a denial of service attack. This is a type of out-of-bound read security flaw. The TCG notes that the flaw occurs in the CryptHmacSign function due to improper validation of a message digest or hash via the hash-based message authentication code (HMAC) signature scheme, leading to an out-of-bounds situation. TCG explains in its VRT0009 advisory: The Common Vulnerability Scoring System (CVSS) score of the flaw is 6.6 indicating a medium level of severity. This is typically the case for most local-level attacks as in order to exploit such a flaw, the threat actor must have physical access to a device. Regardless, AMD has issued firmware to patch the vulnerability on Ryzen 7000, 8000 (Zen 4) and Ryzen 9000 (Zen 5) parts. AMD has confirmed that AGESA (AMD Generic Encapsulated Software Architecture) firmware Combo PI (Platform Initialization) 1.2.0.3e mitigates the flaw. The company notes that the said firmware fixes "ASP fTPM + Pluton TPM" issue. If you are wondering, ASP refers to AMD Secure Processor which is "a dedicated hardware component embedded in every system-on-a-chip." AMD's motherboard vendor partners like Asus and MSI have already begun rolling out the firmware update. MSI has a blog post about the 1.2.0.3e Combo PI as it mentions several new upcoming features including support for new CPUs, better memory compatibility, and more. MSI writes: Interestingly, Asus notes that this firmware update is irreversible as it is a major release. Thus one would hope that it is a very stable release and given that this is the "e" stepping of the firmware, there are pretty good chances of that. Other vendors like Gigabyte and ASRock are yet to release their updates.
    • Really?? Having a sense of humor is a sign of intelligence...what does that say about someone who totally misses the joke and can only respond by parroting a political talking point they heard others make?
  • Recent Achievements

    • Apprentice
      Wireless wookie went up a rank
      Apprentice
    • Week One Done
      bukro earned a badge
      Week One Done
    • One Year In
      Wulle earned a badge
      One Year In
    • One Month Later
      Wulle earned a badge
      One Month Later
    • One Month Later
      Simmo3D earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      604
    2. 2
      ATLien_0
      281
    3. 3
      +FloatingFatMan
      179
    4. 4
      Michael Scrip
      151
    5. 5
      Steven P.
      111
  • Tell a friend

    Love Neowin? Tell a friend!