Recommended Posts

OK, I will try to reduce my posts in this thread. Sorry about last few days bumps.

Reduce? Why?

I much prefer visiting here than at mozillazine! Bunch of fanboys, you have a bad thing to say and are automatically accused of being incompetent/idiot, a Chrome fanboy or know nothing about Firefox!

Here I feel when can discuss in civil way without fanaticism!

And after all this is "Firefox Next" so it is expected to be full of development news!

Mods are you against the updates Zlip is posting?

  • Like 2

Even I think Zlip shouldn't reduce frequency of posting , it is great to read here and keep track of development. He does a great work! :)

Some mockups and stuff about UX : https://wiki.mozilla...User-Experience

You can track this bug to see how many blocking bugs are remaining to be fixed for elm to mc merge : https://bugzilla.moz...gi?id=elm-merge

Snappy Minutes : https://wiki.mozilla...py_.5BWeekly.5D

It is to enable system wide codec to support MP3 and H.264 codecs for Windows Vista+, it is preferred off due to few reasons.

Apparently it is not that good,

https://bugzilla.mozilla.org/show_bug.cgi?id=823168

:rofl:

Reduce? Why?

I much prefer visiting here than at mozillazine! Bunch of fanboys, you have a bad thing to say and are automatically accused of being incompetent/idiot, a Chrome fanboy or know nothing about Firefox!

Here I feel when can discuss in civil way without fanaticism!

And after all this is "Firefox Next" so it is expected to be full of development news!

Mods are you against the updates Zlip is posting?

Thanks for your support but I think people only want major news and I might not be good (which I am) in explaining bug real impact on FF performance since I am not FF dev, I only cover bugs important which I seem in Inbound (Incoming branch) of Firefox but people prefer only stuff which gets landed and not backout and is of big impact.

I don't know what to do but I think I have to wait for people opinion more.

Even I think Zlip shouldn't reduce frequency of posting , it is great to read here and keep track of development. He does a great work! :)

Some mockups and stuff about UX : https://wiki.mozilla...User-Experience

You can track this bug to see how many blocking bugs are remaining to be fixed for elm to mc merge : https://bugzilla.moz...gi?id=elm-merge

Snappy Minutes : https://wiki.mozilla...py_.5BWeekly.5D

Thanks for your support, yes you are right that development is on going so obviously updates from my side will be frequent.

Lets see what other say.

Apparently it is not that good,

https://bugzilla.moz...g.cgi?id=823168

:rofl:

Already know about it and several other regression and performance impact it made. But overall it is positive step in right direction.

  • Like 3

Thanks for your support but I think people only want major news and I might not be good (which I am) in explaining bug real impact on FF performance since I am not FF dev, I only cover bugs important which I seem in Inbound (Incoming branch) of Firefox but people prefer only stuff which gets landed and not backout and is of big impact.

I don't know what to do but I think I have to wait for people opinion more.

.

+1 that's the reason I visit this thread.

Question for anyone else using Nightly and has an Outlook.com email:

Is the chat (The button next to the settings) working for you? The icon is greyed out for me on Outlook.com, but it works everywhere else, like in Skydrive.

Just tried now and Yes it is working fine on my side.

anyone know why they havent updated the UX stub-installer since the 11th? ok just checked, they have removed the 32bit stub-installer in UX.

wondering if a Mod may wanna EDIT the first post an Add this URL instead for the UX Downloads http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-ux/

Just tried now and Yes it is working fine on my side.

That's so strange. I even tried a fresh install of Nightly with no add-ons, and it still looks like this:

ahFFa.png

Again, it works in SkyDrive, and People, but in Outlook, it just doesn't. I saw an older bug that mentioned this, but it was reported fixed. Indeed, the chat worked for me for a little while earlier, but I don't know when it stopped.

Was nothing new reported?

I believe you, I'm just wondering if there's something I'm missing. It did work before. :( .

Do you changed some settings? In outlook? Or used your this account somewhere else with some other services?

It seems it was adblock or something in the hosts file that was causing problems.

But... then why would the chat still work on the other pages and in other browsers? I ask because blocking something in the host file should block everything, regardless of the program, right?

So what was Firefox and Nightly doing differently that caused the chat to be blocked only on Outlook.com and only in Firefox, but nowhere else.?

Another strange problem. Earlier, with the host file still modified, and adblock still running, at some point, the messenger actually loaded once. But that was the only time it did. Makes it seem like it actually does load, but just takes a long to do so. I don't have the technical knowledge to figure this one out.

The tiny minority that actually needs them can be happy now, and the random people who have no idea why they shouldn't be using them will get to complain about the crashes without loading up Mozilla's systems with them.

It's a win-win basically.

The tiny minority that actually needs them can be happy now, and the random people who have no idea why they shouldn't be using them will get to complain about the crashes without loading up Mozilla's systems with them.

It's a win-win basically.

Would you please explain why they should not be used? From what I have read 64 Bit Browsers are more secure? I used Fx 64 Bit for a long time, I stopped when Mozilla said that they were no longer going to develop them. I would like to know why?

Windows 64-bit is now Tier-3 and not much priority plus they are planning to disable crash reporter so I think it is more like nightmare... Because once in future they enabled Firefox 64-bit to Tier 1 etc, all their crash reporter servers surely gonna crash because of lot of unknow crash signature coming in...

Very bad technical point of view decision...

Windows 64-bit is now Tier-3 and not much priority plus they are planning to disable crash reporter so I think it is more like nightmare... Because once in future they enabled Firefox 64-bit to Tier 1 etc, all their crash reporter servers surely gonna crash because of lot of unknow crash signature coming in...

Very bad technical point of view decision...

I do not know why it was crashing on users. The 32 Bit Crashed many many times. I , to the best of my knowledge have never had a crash using the 64 Bit version. Maybe some users don't know where to find the proper plug-ins, IDK. But I agree with you Zippy, it is a very bad decision on Mozilla's part.

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

    • 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.
    • 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.
  • 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!