Recommended Posts

Actually, I think it will autoupdate to the next nightly build. I only got updates once a day until I turned off autoupdating. Either way, you don't have to uninstall, you can always install any Minefield (or Firefox) build on top of what you have installed (if you go from Firefox to Minefield or vice versa you'll have to specify where you want it installed, in my case I just keep it in C:\Program Files (x86)\Mozilla Firefox, so that way when it gets to the RC stage I can stop using Minefield builds and I won't have 2 separate installations). I recommend you only go forward in your upgrading, though; downgrading to an older build, especially if it's significantly older, may break your profile, though I've never had any issues with that myself.

Ok, so if I install the "tinderbox" over my "latest-trunk" will it update every hour or must I uninstall & reinstall?

You need to download each hourly manually , but u can update the nightlies ,,, this also means that the hourly would be updated to nigthly(when out)

Mine also says b3 ;)

and it looks good even with tabs on bottom.

post-251611-12797061649045.png

Which theme? (Is it for 7?)

Does anyone know if Mozilla plans to have inactive tabs non-transparent? I find it very annoying having the tabs transparent atm.

Going by the mockups it looks like the inactive tabs should not be transparent.

The mockups tabs are more opaque but they are transparent. I don't know if the UI team will change this.

Firefox Sync

Alex Faaborg:

  • Top priority now.

Download Manager
Alexander Limi:
  • No changes this week, but plan to get in touch with Paolo, who I talked to about this at the Summit.

Main window refresh

Stephen Horlander:

  • Most of the major pieces are in.
  • Still need progress bar on tabs and combined stop/go/reload.
  • Focus on Windows/Mac on refinement bug fixing.
  • Need to evaluate Bookmarks Menu Button feedback.
  • Next major thing is going to be theming the Window frames/controls for non-Aero configurations ? XP, Aero Basic, Classic.

Other topics covered
Focus for next beta:
  • Location bar improvements
    • Meta bug for the location bar improvements
    • Frank is on the combined stop/reload/go improvements.
    • Design session on Wednesday, also talk about privacy indicators in Larry etc + Privacy Icons + Firefox Menu.
    • Protocol removal/improvements: as early as possible, Frank wants to look at this after stop/go/reload.
    • URL hover design/implementation.
    • AwesomeBar results ? visual design improvements.

    [*]Home/App tabs: dragging + chromeless + right-click to bring controls back + app tab behavior in multiple windows (limi)[*]Doorhanger notifications: not landing in time for next beta, probably later (1-2 betas out)[*]Startup Experience:

    • Meta bug for Startup Experience issues.
    • Run it by Vlad, dbaron or Stuart, identify biggest wins, prioritize.
    • Drawing the window all at once needs to be nominated for blocking the final release ? it looks really broken if we only draw part of the bottom half with the top missing with the new glass theme.
    • Ask on startup, not shutdown for session restore.

http://limi.net/articles/firefox-ux-team-update-17/

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!