Recommended Posts

Stylish not working... I'm on the 4.0 beta 2 nightly as mine says... Why is it Beta 2... When the Menu is still not working! I'm annoyed at having to use the menu to update or change big settings since the new menu is too small and lacks everything.

Because ... it's a beta build. And not even a public beta.

Well I thought I'd try the beta 1 to have a look , and sadly I have to say I'm not impressed at all.

Just my opinion of course .. and I realise it's a beta .. but this can't be near a public release surely ...

It's not, tbh. There's still a couple of months to go.

That's a candidate build, might not end up being the "final" beta.

that's right. if you read the following:

https://wiki.mozilla.org/Releases/Firefox_4.0b1

there could be a 2nd candidate build of Firefox 4.0 beta 1 coming very soon.

Yes 3.7 is skipped as it has been renamed as 4.0 now. Beta 1 will likely be out within 2 weeks.

yup. AND the gecko version number of candidate build 1 of FF4b1 is now 2.0b1 instead of 1.9.3b1.

they've also renamed the gecko version number of the 4.0b2pre nightlies as well (to rv:2.0b2pre).

no more gecko 1.9.3.x.

app tabs are so wide O.o is there a way to fix this?

The same thing happens with me and FaviconizeTab, it's rather annoying :(

I've made my tabs a little smaller, but I still want FaviconizeTab to work, or a similar addon that works.

capturefx.png

wth is taking so damn long? Jesus, take a hint from the Chrome guys and start rolling out the updates, they are dragging their feet with this release aren't they?

not really, they're completely redesigning the UI and this is their first experience going into the titlebar

there's a lot of reprogramming to be done and a lot of mistakes to be learned from and bugs to fix

i'd say their rate of progression is reasonable for what their doing

wth is taking so damn long? Jesus, take a hint from the Chrome guys and start rolling out the updates, they are dragging their feet with this release aren't they?

I agree.

The UI itself should not be taking this long, and in reality should have been completed to the standard of the mockups a long time ago.

  • Like 1

I agree.

The UI itself should not be taking this long, and in reality should have been completed to the standard of the mockups a long time ago.

Yup, especially considering what you managed to do laugh.gif

  • Like 1

How do you get app tabs in 4.0 beta 1?

i don't think it's truly implemented yet

i think people are just using an extension atm

I agree.

The UI itself should not be taking this long, and in reality should have been completed to the standard of the mockups a long time ago.

if you think it's so easy why don't you do it yourself

it's not as easy as you think, with every little thing that they change brings the possibility of a bug or and issue that they'll then have to fix, it's a long and grueling process of much trial and error

Yup, especially considering what you managed to do laugh.gif

Thanks! :D

i don't think it's truly implemented yet

i think people are just using an extension atm

if you think it's so easy why don't you do it yourself

it's not as easy as you think, with every little thing that they change brings the possibility of a bug or and issue that they'll then have to fix, it's a long and grueling process of much trial and error

I'm talking about the theme itself, and if you think I'm not familiar with the process you're mistaken.

(Y) And the new titlebar design shouldn't be used as an excuse, look at how quickly Opera inplemented their design.....

Yup, and what's taking them so long to implement the options within the menu is also beyond me. SoapyHamHocks can add an option to one of our menus in seconds if needed.

  • Like 1

Yup, and what's taking them so long to implement the options within the menu is also beyond me. SoapyHamHocks can add an option to one of our menus in seconds if needed.

Perhaps they don't want to do it fast, they want to do it right. Sounds clich?, but quite likely true.

Perhaps they don't want to do it fast, they want to do it right. Sounds clich?, but quite likely true.

exactly what i was trying to say, better to take your time and do things right then throw it together quickly and have tons of bugs

exactly what i was trying to say, better to take your time and do things right then throw it together quickly and have tons of bugs

I understand your opinion, but because of BoneyardBrew and SoapyHamHocks, there isn't too much of an incentive for me to move to a less stable Firefox pre-beta, when my 3.6.6 looks almost exactly like these current builds.

exactly what i was trying to say, better to take your time and do things right then throw it together quickly and have tons of bugs

There are not tons of bugs. The remaining bugs are few and do not effect stability. The Public Beta should be out tonight or tomorrow.

There are not tons of bugs. The remaining bugs are few and do not effect stability. The Public Beta should be out tonight or tomorrow.

He saying that if they did try and rush development there would be lots of bugs. Not that there are currently.

FWIW, there are a fair number of bugs/issues in beta 1, but few are major. (This is me managing expectations)

I don't even think the current Firefox menu is staying, I think they're going for a Office style split menu.

I personally wouldn't like a Chrome style update system, Chrome gets features rushed out that can then break (like WebSockets, the spec changed in a breaking way, so the current Chrome release can't talk to servers implementing the current spec, which is needed for Firefox 4 and dev builds of Chrome)

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

    • No registered users viewing this page.
  • Posts

    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
    • wow. that color finally comes to Surface Pro. was always a little jelly when a friend had the sandstone Surface Laptop. I wonder how different this dune is from the sandstone. I'll be getting the dune version. always thought black and platinum were a little boring. I'll still have access to my blue Surface Pro 11 as it'll be a hand-me-down.
    • Looks a very subjective aren't they!? I like its simple design. I love the way Apple designs their products with function over form, minimalization, and simplicity over cluttered complex designs. Many, not all, of their products follow this trend, and the device becomes a tool rather than dominating the space. I do not however like their OS. I have never bought a Apple product, and while I'd consider the Neo for my wife, I am hoping there are better alternatives out there when her failing MacBook Pro 2017 finally stops. Fischer-Price is famously plastic, garish, and poorly made. Basically you're describing the Window Laptops the Neo competes against! This is how product design should be, and what Apple have often followed in recent years: https://tenprinciples.design/
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!