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

    • Wonder what MPs have ties to these privacy/verification/data harvesting companies that are going to step in this time. Last time under the Tories half the cabinet had fingers in the pies, heck even the PM and his wife at the time was working for silicon valley, probably made a fortune.
    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • 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
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!