Recommended Posts

So they got rid of the big back button in the desktop version, but decided to keep it for Metro?

It makes sense, it's designed for tablets and you don't have the same fidelity with selecting things there as you do with a mouse and keyboard.

It makes sense, it's designed for tablets and you don't have the same fidelity with selecting things there as you do with a mouse and keyboard.

Is there even mockups though for the desktop version without the big back button? Curious as I am wanting to see how it looks.

Now you camn't send a link or image via a context menu anymore. Is Mozilla trying to force users away? This sucks.

post-293012-0-51060400-1341512353_thumb.

PS : They are implementing Social API which will make "Send"; "post on facebook / twitter etc" , and the functionality of send (which never sent stuff but emailed) is now of Email <link>

post-293012-0-51060400-1341512353_thumb.

PS : They are implementing Social API which will make "Send"; "post on facebook / twitter etc" , and the functionality of send (which never sent stuff but emailed) is now of Email <link>

I do not use FB or any social api BS. I also do not have the menu bar open to get to the email image or link. Below is what I have to do to send a link:

So for me to now send a link I have to :

1. Right Click on a link

2. Open up the menu bar

3. Click on File

4. Open email link

5. then send link.

Prior to this "Fix" all I had to do was RC and send link.

This is insane.

I do not use FB or any social api BS. I also do not have the menu bar open to get to the email image or link. Below is what I have to do to send a link:

This is insane.

You can't email links now , but you can email images , from context menu.

and? that can still be considered social interaction

Maybe so but it is not being forced upon me. Posting in the Forum is a social interaction. Just getting on the Net is a social interaction unless your a bot. Anyway after sleeping on this, I can't remember the last time I did send a link and as bgas said you can still send an image. What I will not go for will be the integration of FB and Twitter into Firefox. And if you read deep enough that is what Asa wants.

There are only three people in whole mozilla... I want to kick or fire them...

Asa, Stephen Horlander and Dao...

Asa for his garbage decisions.

Stephen for his ugly work of Australis

Dao for making irreverseable changes.. (close other tab warning)

  • Like 3

Per Tab memory reporting landed in Inbound: https://bugzilla.moz...g.cgi?id=687724

how about kill tab memory when close, otherwise, firefox is still full of memory garbage

And you're right dude, Asa should be cast in into coding exile and to never program anything again. The man is full of ego.

I'd kick whomever is responsible for making Firefox D2D work only on a subset of hardware which is capable of D2D.

It's because testing (and ensuring fixes for) all possible combinations is something beyond Mozilla's capabilities. Unfortunate, but certainly not an arbitrary decision.

how about kill tab memory when close, otherwise, firefox is still full of memory garbage

Uh, this already happens. If it's not all being freed up, it likely due to addons holding onto it. In any case, preventing addons from doing that is a current focus.

It's because testing (and ensuring fixes for) all possible combinations is something beyond Mozilla's capabilities. Unfortunate, but certainly not an arbitrary decision.

Firefox probably makes some DirectX calls which not all GPUs support whereas IE9 does not.

Thus trace IE9, compare with Firefox, make fix.

Alternatively, get GPU which is blacklisted in Firefox and works in IE9.

Spam debug statements before all DirectX calls - run Firefox - Firefox will crash but print statements will tell what call was being made.

Not sure why this is a problem.

how about kill tab memory when close, otherwise, firefox is still full of memory garbage

And you're right dude, Asa should be cast in into coding exile and to never program anything again. The man is full of ego.

You said it alll he had on his blog was that home he was build. like what did he think he was the only one that can have a log home. He needs to go work for Opera!

Lack of resources. The IE team have a huge computer farm to do their testing on, for example - Mozilla do not. They just have to be more selective in where they point their effort.

And Firefox and IE9 use Direct2D in different ways, Firefox is being hit by bugs that IE9 isn't, even when the drawing calls are the same (The whole "flickers on resize" issue being one of them)

For a while, some drivers caused menus in Firefox to render as solid black rectangles, IE9 never had that issue since it doesn't use Direct2D for it's UI, etc.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • 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!