Recommended Posts

Hmmm pinch.gif

By the way are you planning a Firefox theme to go with your Windows theme?

My Windows theme :blink: Maybe you mean Dom's theme? I think his theme has a lot of potential to work as a Firefox theme. Knowing us we will probably end up doing it after Minimal, TwentyTen, Metro, and all those others we have had on the back burner for a while.

There was something planned with the "Home Tab" but I think that's been scrapped.

Yeah, the Home Tab got scaled back a whole lot, currently it's just a google search box and news items from Mozilla.

Lots of stuff got scaled back/cut though, like browsing bookmark folders in content. But it can always come back in the future, since the foundation is there at least.

My Windows theme :blink: Maybe you mean Dom's theme? I think his theme has a lot of potential to work as a Firefox theme. Knowing us we will probably end up doing it after Minimal, TwentyTen, Metro, and all those others we have had on the back burner for a while.

lol yes, sorry I get you two confused some times! blush.gif

With a bunch of [softblocker] bugs which make FF4 slower than FF3.6

EDIT: What I am trying to say it that [hardblocker] bugs are not the only things you want them to fix.

Yeah, that first line made no sense. Blockers are blockers based on their specific issue ... they generally have little relevance to performance compared to 3.6 - they could be issues within new functionality, or new functionality itself.

The continued existence of a blocker doesn't mean the product is broken - just something wanted isn't there yet, which could be many things.

So what is the difference between this list of bugs:

https://bugzilla.moz...cking2.0:betan+

and this one:

https://bugzilla.moz...final%20sw:hard

first one is the list of bugs which were SUPPOSED to be fixed for the betas (soft + hard + others blockers)

while the second list has bugs which are MUST to be fixed for the betas (hard blockers)

Fonts look bad due to a Microsoft bug that is only evident when hardware acceleration is used. The best fix ATM, rather than turning hardware acceleration completely off in Options, is to just turn the text stuff off using about:config, adding an entry...... gfx.direct2d.disabled and set it to boolean TRUE and restart Firefox 4.

And now they're hiding one of the major new features of Firefox 4.0 from the user in the default config:

Actually, after talking with Limi, we've decided that the safest way forward will be to remove the Panorama button from the toolbar by default. Users can customize their toolbar to re-add it, or use the menu options to get in/out.

I'll file a bug to track that work, but for now let's take this off the list. I suspect Ian will agree, as he'd mentioned that this was one of the riskier changes left.

Source: Bugzilla@Mozilla

Read the discussion following the comment quoted above. Joe User sticks to the default settings most of the time - removing the toolbar icon makes it undiscoverable to most of the Firefox userbase. IMHO Mozilla might as well remove Panorama entirely from 4.0 and re-add it in 4.next.

Then again I consider Panorama an idea which looked good on paper, yet feels over-engineered and buggy when you actually use it.

Good grief... beta 9 is utter crap...

My window flickers like hell, it eats even more memory, it slows down fast... What the heck?

Glassed Silver:mac

Anyone know if they've fixed isolated cases of the browser freezing or stuttering on a cold start of the browser? I can easily see this happen by starting the browser, navigating to Neowin, and then scrolling up and down.

This is on beta 9 with a system that usually runs off a Intel HD Graphics chip.

I've had all these problems with beta 9, beta 8 was much better in those regards :(

Same here... beta 8 was rock solid compared to this POS...

To go even further, I much prefered any beta I tried before: 4, 6 and 8 have been awesome...

Glassed Silver:mac

Joe User sticks to the default settings most of the time - removing the toolbar icon makes it undiscoverable to most of the Firefox userbase. IMHO Mozilla might as well remove Panorama entirely from 4.0 and re-add it in 4.next.

Then again I consider Panorama an idea which looked good on paper, yet feels over-engineered and buggy when you actually use it.

Leaving it in allows them to get more feedback on it than leaving it out. Removing it is also likely a much bigger challenge.

Good grief... beta 9 is utter crap...

My window flickers like hell, it eats even more memory, it slows down fast... What the heck?

Glassed Silver:mac

Apparently *some* of beta 9's issues are fixed in a later trunk build (as problems I had with b9 I don't have with the current Minefield, which is b10pre) - some fixes failed to beat the clock?

Apparently *some* of beta 9's issues are fixed in a later trunk build (as problems I had with b9 I don't have with the current Minefield, which is b10pre) - some fixes failed to beat the clock?

I dislike Minefield's name and icon, hence I don't install it, but most likely yes I suppose...

Oh well... At this rate I will have b10 by next week or so :p

Glassed Silver:mac

Leaving it in allows them to get more feedback on it than leaving it out. Removing it is also likely a much bigger challenge.

I like TabCandy Panorama, but I think it was added a bit too late into the process, since it's been nothing but bug fixes and regressions.

I'll keep using it though, since I often have 30+ tabs open for distinct reasons.

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

    • No registered users viewing this page.
  • Posts

    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
    • Thanks for the advice guys, I'll give my current GPU a clean and then run the benchmarks to see how similar it is. Hopefully a bit of a clean-out will help it last a bit longer.
    • Pretty sure those will still be in this game. The series' well-explored psychosis themes will return as well.
    • "performance issues? what performance issues?!"
    • Microsoft making much needed change to Windows 11, 10 Patch Tuesday security updates by Sayan Sen Recently, Microsoft delivered its latest Defender patches for Windows 11 ISOs. These definitions are released from time to time alongside the general security updates available during Patch Tuesday. Speaking of Defender, the company has now announced another important change that affects how security updates are delivered to enterprise devices running Windows. According to a recent announcement, Microsoft Defender for Endpoint's endpoint detection and response (EDR) updates will no longer be bundled with the monthly Windows security updates or Patch Tuesdays. Instead the company is shifting delivery of these updates to Microsoft Update, bringing EDR servicing in line with several other Microsoft Defender components. If you recall, Microsoft last year moved PowerShell updates to Microsoft Update (MU) as well since it provides automatic updates for Microsoft products and services. Thus the move is intended to allow Microsoft to deliver EDR improvements and security enhancements independently of the OS's regular monthly update cycle; this should enable faster deployment of protection updates without requiring organizations to wait for the next Patch release. For those unfamiliar, Microsoft Defender for Endpoint's EDR capabilities are designed to help organizations detect, investigate, and respond to advanced threats across managed devices. Keeping these components updated is critical for maintaining protection against evolving attack techniques. The rollout has already began for Windows 10 devices in late May 2026 (last month) and Microsoft says it will gradually expand support to Windows 11 and the remaining supported Windows versions over the coming months. The company expects deployment across Windows 10 and Windows 11 to be completed by fall 2026 or around Q3 of this year. Once the transition is complete, EDR updates will be delivered through Microsoft Update using KB5005292, provided the required prerequisite updates have already been installed. Microsoft is also introducing a new Defender Update Service as part of the change. Following installation of the first update, devices will automatically create a new directory located at %ProgramData%\Microsoft\Microsoft Defender\Defender Update. Microsoft notes that restarts may occasionally be necessary in case of "rare" failure scenarios. For most organizations, the tech giant says no action will be required as long as Microsoft Update is already permitted within their update management strategy. Admins who rely on manually deployed update packages, however, will need to adjust their processes to ensure the new Defender update package is included. Microsoft also recommends reviewing internal documentation and notifying helpdesk and security operations teams about the updated delivery mechanism to avoid confusion during the transition. As a prerequisite, the tech giant notes that systems must be running Sense version 10.8798.25857.1000 or later and have one of the following Windows updates (or later) installed: Win11 24H2 KB5062660 (2025-07 Cumulative Update Preview) Win11 23H2 KB5062663 (2025-07 Cumulative Update Preview) Win11 22H2 KB5062663 (2025-07 Cumulative Update Preview) Win10 22H2 KB5062649 (2025-07 Cumulative Update Preview) Win10 1809 KB5063877 (2025-08 Cumulative Update) Server 2019 KB5063877 (2025-08 Cumulative Update) Server 2022 KB5063880 (2025-08 Cumulative Update) Server 2025 KB5063878 (2025-08 Cumulative Update) As always, organizations should verify that their update policies align with the new servicing approach before the broader rollout reaches all supported Windows platforms later this year. In case of major problems, the EDR update can be rolled back to the inbox version stored in %ProgramFiles%\\Windows Defender Advanced Threat Protection (ATP) using: MpCmdRun.exe -RevertMde -Product Edr -ToVersion Inbox For those who have access to the Microsoft 365 Admin Center portal, you can view the message here under ID MC1381119.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      73
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!