News for hackers. Stuff that matters.
Re:Firefox 52 released by bzbarsky on Tuesday March 07, 2017 @01:35PM (#13813202)
This shouldn't be happening. We have explicit code to force view-source to read from the cache instead of hitting the server...

If you can reproduce this problem in a clean profile, please file a bug, cc "bzbarsky", and I'll take a look. Obviously, steps to reproduce would he helpful too.

If it doesn't happen in a clean profile, then we start looking into what's special about your existing profile.

Re:Firefox 52 released by mconley on Tuesday March 07, 2017 @02:20PM (#13813712)
Please cc me too. (mconley at mozilla dot com)
Re:Firefox 52 released by Joeboy on Tuesday March 07, 2017 @03:08PM (#13814241)
Ok now I have to do some embarrassing backtracking. In a clean profile I don't get the problem. Sorry for publicly whining about your product, which apparently works fine.

I'm not sure what I've done to make it not work here, but this profile dates from a long time ago so maybe it's just cruft or an extension behaving oddly. I'll switch to using a clean profile. Sorry again and thanks for your attention.

Re:Firefox 52 released by bzbarsky on Tuesday March 07, 2017 @11:51PM (#13817984)
Thank you for checking that!

If you still have the profile where it doesn't work, and are willing to do some detective work to figure out what it is that doesn't make it work (e.g. extensions or prefs.js or something else), that would be awesome. You're hardly the only Firefox user with a somewhat old profile, and it's possible that there's something specific going wrong that we should be handling better on our end...

Re:Firefox 52 released by nnethercote on Tuesday March 07, 2017 @07:53PM (#13816823)
This is a nice way to refresh your profile without losing all your history and other stuff: https://support.mozilla.org/t5/Procedures-to-diagnose-and-fi...
Re:Firefox 52 released by mconley on Tuesday March 07, 2017 @06:37PM (#13816341)
All good. Thanks for checking. :)