Firefox 3.7 and 4.0 theme and UI revamp - Mac specific visual refresh


Recommended Posts

Mac Theme/UI Refresh for Firefox 3.7

Fx-3.7-Mockup-Mac-i03-Tabs-Hanging-Large-Back.png

The overall design changes for Firefox 3.7 on Mac are mostly the same as what is being proposed for Windows. Structurally they are very similar with a notable exception:

  • The Menu Bar: The Menubar on Mac is different from its counterpart on Windows. There is no system wide push to phase it out and it is an integral platform UI element.
  • Page and Tools Buttons: Since the Menubar is not being changed these buttons will not be on by default. They can be added from the Customization sheet if desired.

In addition to the structural changes already proposed the Mac theme is primarily focusing on visual design changes.

[...]

Mac Theme/UI Refresh for Firefox 4.0

Fx-4.0-Mockup-Mac-i03.png

Visual Styling

Style changes from 3.7 to 4.0 are fairly minimal except for new elements that must be styled:

  • Extensions Area: Proposed idea is to be stylistically different from the rest of the toolbar. Lighter and slightly raised.
  • Identity Button: The Identity button can be seen in the upper right of the mockup. The idea is to be attached to the window, much like a label or a tag.
  • Search Selector Style: This area is still not fully developed. An idea is to have the search selector change color based on which search is being used.

souricon.gif News source and full article: MozillaWiki

Tabs on TOP!!!! :drool: :drool: :drool: :drool: :drool:

Tabs on TOP!!!! :drool: :drool: :drool: :drool: :drool:

Tabs on TOP!!!! :drool: :drool: :drool: :drool: :drool:

Tabs on TOP!!!! :drool: :drool: :drool: :drool: :drool:

Tabs on TOP!!!! :drool: :drool: :drool: :drool: :drool:

One thing that I don't like about the tabs-on-top style with OSX compared to Windows (When using Google Chrome) is that under Windows when you maximize the window the extra title bar space goes away and the tabs become flush with the top of the window. With OSX that doesn't happen and it seems a bit awkward.

I absolutely love the 4.0 mockup. I have been using Safari 4 exclusively for a while now, but I'll definitely install Firefox 4.0 with that theme... I loved the tabs over the location bar in the Safari 4 beta and the load bars are wonderful in both designs!

The main window chrome may look good, but the whole thing still feels like a shoddy port.

That's the biggest problem I have with Firefox. It just doesn't have the fluidity and behavior of a normal Mac application.

They are ok but I still prefer GrApple themes - http://www.takebacktheweb.org/

Just a personal opinion, but I really find that scheme soul-destroyingly boring. Beige, beige and more beige. Apart from the built in OSX colours, there's no variety at all.

But! at least Delicious and Luscious have the tabs the right way around. :)

Just a personal opinion, but I really find that scheme soul-destroyingly boring. Beige, beige and more beige. Apart from the built in OSX colours, there's no variety at all.

But! at least Delicious and Luscious have the tabs the right way around. :)

Beige? You might wanna check the colors on your monitor. :p

The progress bar looks really out of place. In the 4.0 mockup it should be at the bottom of the tab, not at the top of it, and be stretched to cover all the tab on length.

The rest looks really smooth, I really like it, I'm waiting to see what are they going to do with the bookmark bar and how it will blend with the "extension buttons" backround.

Yes, beige: http://en.wikipedia.org/wiki/Beige

So it's darker than beige. But it's that area of the spectrum. Ecru, maybe.

I don't really wanna start something here (because this would kind of be a stupid thing to argue), but where's the beige?

I see shades of gray and some blue in the Bookmarks sidebar. I even just analyzed it with xScope and everything is definitely a shade of gray (which is what Leopard's standard metal look is). There's nothing even remotely beige or ecru in there.

I don't really wanna start something here (because this would kind of be a stupid thing to argue), but where's the beige?

I see shades of gray and some blue in the Bookmarks sidebar. I even just analyzed it with xScope and everything is definitely a shade of gray (which is what Leopard's standard metal look is). There's nothing even remotely beige or ecru in there.

Soooo ... I was using Firefox in Windows to view it.

I went ahead and saved one of the images to disk, and opened it in Windows Photo Gallery (default image viewer in Windows Vista) ... definite brown tinge.

Then I open it in Fireworks: totally gray. IE8: totally gray. Chrome: totally gray.

That's really odd. Somewhere along the way for Firefox, the color correction is messed up.

Anyone else got a Windows PC to test? Try it on Firefox 3.5 :) I know Firefox has more advanced colour controls than IE, so wondering whose fault it is :p

Bugger: it's my Firefox colour management profile. If I switch it off as described on https://developer.mozilla.org/En/ICC_color_...olor_correction ... boom! Silver!

So now I either blame my monitor's colour profile, or Firefox's handling of it. Weird that I've not noticed this issue before.

/me is getting new monitor drivers

Update: I give up. I believe it's the ICC profile for my 2208WFP (problem also noted at http://forums.techguy.org/digital-photogra...rey-brown.html), but for now, I don't seem to be able to fix/remove it. I'll probably just wait until I install Windows 7 later this month, and avoid downloading the monitor update from Windows Update. What fun!

Apologies for the deviation from the topic, hope it was interesting at least :)

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

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!