Recommended Posts

Is there any way to get the "URL preview" back, like it was in beta 10, and turn off the "bloody stupid" status display in the bottom left corner?

1 - Not Yet

2- http://userstyles.org/styles/43680

#statusbar-display {
    display: none !important;}

Is there any way to get the "URL preview" back, like it was in beta 10, and turn off the "bloody stupid" status display in the bottom left corner?

evidently devs thinks chrome is better, since they felt the duty to copy it :/

evidently devs thinks chrome is better, since they felt the duty to copy it :/

It's not a beloved feature for every Chrome user! Here's one point of view:

http://www.google.com/support/forum/p/Chrome/thread?tid=3236567c895e1320&hl=en

So Fx 4 beta 11 won't even have an "either/or" option?

It's not a beloved feature for every Chrome user! Here's one point of view:

http://www.google.com/support/forum/p/Chrome/thread?tid=3236567c895e1320&hl=en

So Fx 4 beta 11 won't even have an "either/or" option?

Firefox has become a Chrome wannabee. I am disgusted with it.

I'm using Fx 4 beta 10 on Win XP with tabs on top and no menu bar.

I want to change the color of the space lying between the appmenu-button and the tabs, between each tab, and between the last tab on the right and the min/max/close buttons on the far right. Currently, this space is a solid-blue when Firefox is in focus and grey when any other window is active (Win XP defaults?).

hey can anyone gimme the script to make the empty navigation toolbar of minimal width, say 2 or 3 px. Currently its in this condition :

ff4b12prenav.png

why not right click and remove it?

this worked for me

#nav-bar {

height: 3px !important;

min-height: 0px !important;

overflow: hidden !important;

}

I'm using Fx 4 beta 10 on Win XP with tabs on top and no menu bar.

I want to change the color of the space lying between the appmenu-button and the tabs, between each tab, and between the last tab on the right and the min/max/close buttons on the far right. Currently, this space is a solid-blue when Firefox is in focus and grey when any other window is active (Win XP defaults?).

Got it...

#TabsToolbar { background: desired_color !important; } but the color doesn't change when the browser isn't in focus. Any idea about that?

Got it...

#TabsToolbar { background: desired_color !important; } but the color doesn't change when the browser isn't in focus. Any idea about that?

How about adding:

#TabsToolbar:hover{ background: desired_color !important; }

How about adding:

#TabsToolbar:hover{ background: desired_color !important; }

Gary, thanks! But I think what I want is like when I hit alt+tab to bring up a window of another program, say Notepad, the "desired_color" in the TabsToolbar area should be different to signify that Firefox is not the active window. Previously, without any code regarding TabsToolbar, the area would be a dark blue when Firefox was active and if I switched to another program, the area of the TabsToolbar not occupied by tabs would automatically turn grey.

In edit: this is with Firefox in a maximised window and the other program's window not maximized.

Gary, thanks! But I think what I want is like when I hit alt+tab to bring up a window of another program, say Notepad, the "desired_color" in the TabsToolbar area should be different to signify that Firefox is not the active window. Previously, without any code regarding TabsToolbar, the area would be a dark blue when Firefox was active and if I switched to another program, the area of the TabsToolbar not occupied by tabs would automatically turn grey.

In edit: this is with Firefox in a maximized window and the other program's window not maximized.

I guess something like this is involved ... #main-window[sizemode=maximized][tabsontop=true] but what happens next is beyond me.

Of course, I could just remove this bit (#TabsToolbar { background: maroon !important; }) and go back to the default colors ...

As promised. Let me know if there are any issues.

post-49492-0-54742900-1294174232.png

Download

Ok I realise its a late reply, but I just tracked this down to this extension:

capturevpk.png

What appears to happen is the address bar on popup windows and forms appears on the titlebar, and so not only can I not move the window, but I can't edit the address either. Thanks to Aero's chunky buttons and window glow, I can still use the window widgets, but nothing else!

Ok I realise its a late reply, but I just tracked this down to this extension:

http://img844.imageshack.us/img844/6349/capturevpk.png

What appears to happen is the address bar on popup windows and forms appears on the titlebar, and so not only can I not move the window, but I can't edit the address either. Thanks to Aero's chunky buttons and window glow, I can still use the window widgets, but nothing else!

I had this also when using this extension.

I guess something like this is involved ... #main-window[sizemode=maximized][tabsontop=true] but what happens next is beyond me.

Of course, I could just remove this bit (#TabsToolbar { background: maroon !important; }) and go back to the default colors ...

Did you see this, it's the solution to your problem:

What you need is

#TabsToolbar:-moz-window-inactive {background-color: red !important; }

Did you see this, it's the solution to your problem:

Thanks, foxxyn8. Was just what I needed.

Here's a slightly weird question ....

Once we decide we like some code, is it better to place it in userContent.css or userChrome.css and keep Stylish for code that won't work in userContent.css or userChrome.css? Of course, as long as something is being tested, Stylish is more convenient since a browser restart is not required.

Would that be more efficient in any way?

Personally, I just keep it all in stylish because it allows me to enable/disable on the fly which makes it easier to track conflicting styles and test new styles. There are also some things that just can't be styled using userChrome/userContent.

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

    • No registered users viewing this page.