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

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, unpacking and setting up the smart scope + tripod for equatorial tracking, mucking around with settings, maybe shoot some calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • 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.
  • 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
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!