Recommended Posts

Wait for them to fix Direct2D rendering.

That, along with bug fixes to the next rendering code, should perfect it.

D2D should help, but not by that much.

Direct3D/OpenGL backed layers will have the greatest benefit (along with the tile cache or whatever caching method they use)

one weird thing i've noticed

if you try to go to some sites like live.com it will take you to the mobile version, is there a way to fix this?

Its coz of UA

go to about:config

Set

general.useragent.extra.firefox

as Firefox/3.6.6 or Firefox/3.6.7 etc

i just changed it from minefield to firefox and that did the trick, odd that that would cause that kind of problem

thanks though

yeah that too would fix the problem , but the thing is some sites don't treat Firefox 4.0 as a browser , so that's why... I myself use Firefox/3.9 :p (Orkut doesn't support 4.0)

And in any case , if it causes problem , then you can revert back OR set it as a stable version's label, its just Firefox's Hidden Compatibility mode

One big issue with the beta: In W7, if I have a dark or black background - the title of any inactive tabs becomes unreadable. No idea how they would work around that, but its annoying enough to stop me using the beta :(

One big issue with the beta: In W7, if I have a dark or black background - the title of any inactive tabs becomes unreadable. No idea how they would work around that, but its annoying enough to stop me using the beta :(

Made inactive tabs readable, note hover behavior too.

/* Change color of inactive tabs */

tab:not([selected=true]) {

color: #ffffff !important;

}

post-2-12794008126698.png

Can someone help me make the home button the same color as the active tab?

Here's what I have now -moz-dialog doesn't work (tried that).

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

#TabsToolbar > #home-button {

-moz-appearance: none !important;

background: transparent -moz-linear-gradient(left center , transparent, transparent 1px, rgba(128, 128, 128, 0.1) 1px, rgba(128, 128, 128, 0.1)) repeat scroll -6px 0 !important;

background-clip: border-box !important;

background-origin: padding-box !important;

background-size: 200% auto !important;

margin: 0 !important;

padding: 0 1px !important;

-moz-border-image: url("chrome://browser/skin/tabbrowser/tab.png") 3 5 3 6 / 3px 5px 3px 6px !important;

-moz-border-radius: 6px 4px 0 0 !important;

margin-left: 3px !important;

}

#TabsToolbar > #home-button:hover {

background-image: -moz-linear-gradient(left, transparent, transparent 1px, rgba(255,255,255,.4) 1px, rgba(255,255,255,.4)) !important;

}

#TabsToolbar > #home-button > .toolbarbutton-icon {

margin-top: -1px !important;

margin-bottom: -1px !important;

}

post-2-12794013813275.png

Can someone help me make the home button the same color as the active tab?

Here's what I have now -moz-dialog doesn't work (tried that).

post-2-12794013813275.png

the original tabs' background is:

background-image:-moz-radial-gradient(center top , white, rgba(255, 255, 255, 0) 60%), -moz-linear-gradient(left center , transparent, transparent 1px, rgba(255, 255, 255, 0.5) 1px, rgba(255, 255, 255, 0.5)), -moz-linear-gradient(left center , transparent, transparent 1px, #E3EDF6 1px, #E3EDF6);

I've been tweaking my menu button some more. I figured I may as well share since I'm bored. Pictures are represented as normal/mouseover.

Red post-1972-12794410120939.png

#appmenu-button-container{
margin: 0px 0px 4px 4px !important;
}

#appmenu-button{
padding: 2px 10px 2px 7px !important;
}

#appmenu-button dropmarker:before {
padding-right: 5px !important;
}

#appmenu-button{
background: -moz-linear-gradient(top, rgba(251,89,65,1), rgba(189,40,25,1), rgba(157,6,0 ,1)) !important;
-moz-border-radius: 0px 0px 4px 4px !important;
border-top: 0px !important;
margin-top: 0px !important;
}

#appmenu-button:hover{
background: -moz-linear-gradient(top, rgba(251,89,65,1), rgba(251,55,65,1)) !important;
}

Blue post-1972-12794410879444.png

#appmenu-button-container{
margin: 0px 0px 4px 4px !important;
}

#appmenu-button{
padding: 2px 10px 2px 7px !important;
}

#appmenu-button dropmarker:before {
padding-right: 5px !important;
}

#appmenu-button{
background: -moz-linear-gradient(top, rgba(58,127,197,1), rgba(47,119,189,1), rgba(0,58,229,1)) !important;
-moz-border-radius: 0px 0px 4px 4px !important;
border-top: 0px !important;
margin-top: 0px !important;
}

#appmenu-button:hover{
background: -moz-linear-gradient(top, rgba(78,147,229,1), rgba(0,78,213,1)) !important;
}

Green post-1972-12794411488904.png

#appmenu-button-container{
margin: 0px 0px 4px 4px !important;
}

#appmenu-button{
padding: 2px 10px 2px 7px !important;
}

#appmenu-button dropmarker:before {
padding-right: 5px !important;
}

#appmenu-button{
background: -moz-linear-gradient(top, rgba(112,178,66,1), rgba(0,147,14,1), rgba(77,154,6,1)) !important;
-moz-border-radius: 0px 0px 4px 4px !important;
border-top: 0px !important;
margin-top: 0px !important;
}

#appmenu-button:hover{
background: -moz-linear-gradient(top, rgba(112,178,66,1), rgba(82,178,14,1)) !important;
}

If you use these and they don't look the same as my screenshots it may be because I'm using the latest hourly build.

What do you think of this, I modified the Aqua Toolbar script I had (for ages, Vista theme) to your blue button colors, only thing I'm having trouble with is getting the home button to stick, after a restart.. Maybe one of the scripts is conflicting (Tabs in titlebar?)

post-2-12794420592189.png

Ooh. Pretty. Right now app tabs in general still don't stick, so that might be part of it. I'm having an issue that just started (for me) today where if I app tab a page and close all the other open tabs it removes the tab bar completely and mushes my app tab together with my navigation toolbar. Ugh.

You could test your tabs in titlebar hypothesis by disabling the script and seeing if the issue persists. I'm betting it will.

I didn't realize beta 1 didn't have that. I just tested your home button script and it's "sticking" for me, so when beta 2 comes out you should be good to go. Potentially it could be out in 4 days, but we all know how much Mozilla loves deadlines (and the whooshing sound they make as they go racing past).

Cool, I was using the Minefield nightlies, but I got fed up with stuff/extensions getting disabled or breaking with each random update lol.

Thank god for MozBackup, I was able to transfer everything from my laptop and upgrade to FF 4 B1 :D

To anybody who downloaded the buttons I posted this morning, I found that tweaking the top margin slightly looks better (IMO). It won't let me edit the post now so the change is very minor and I'll post it here:

#appmenu-button{

background: -moz-linear-gradient(top, rgba(58,127,197,1), rgba(47,119,189,1), rgba(0,58,229,1)) !important;

-moz-border-radius: 0px 0px 4px 4px !important;

border-top: 0px !important;

margin-top: 0px !important;

}

Might look better if changed to:

#appmenu-button{

background: -moz-linear-gradient(top, rgba(58,127,197,1), rgba(47,119,189,1), rgba(0,58,229,1)) !important;

-moz-border-radius: 0px 0px 4px 4px !important;

border-top: 0px !important;

margin-top: -1px !important;

}

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

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!