News for hackers. Stuff that matters.
Re:Firefox 52 released by sp332 on Tuesday March 07, 2017 @10:28AM (#13811030)
That is annoying, but does the Inspector in the Developer Tools show what you're looking for?
Re:Firefox 52 released by Joeboy on Tuesday March 07, 2017 @10:36AM (#13811100)
As far as I know the way to get the unmodified source in the Developer tools is to find the html request in the Network tab, click on it, go to the Response tab of the small panel on the right and read the source out of said small panel (it's about 65x11 chars here). I'd much, much rather be able to just hit Ctrl-U and read it in a new tab. If there's an easier way then I'd like to know about it.
Re:Firefox 52 released by Drdrdrq on Tuesday March 07, 2017 @12:22PM (#13812370)
For me it suffices, though I too would prefer if "View source" just showed this same content. Maybe an extension could hijack Ctrl-U and display fetched source?
Re:Firefox 52 released by rpeden on Tuesday March 07, 2017 @10:42AM (#13811172)
The difference is that the Inspector shows the page exactly as it exists now, including any DOM changes that have been done via JavaScript. I typically use 'View Source' when I want to see the original page content before anything had been altered.

It looks like the the original commenter is talking about was first reported 12 years ago[1], so I wouldn't count on it being resolved any time soon. It just doesn't seem to be something that many web browser users actually care about, so I don't blame the FF team for not assigning much priority to changing the current behavior, even though I'd also like View Source to work the way way Joeboy is asking for.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=307089

Re:Firefox 52 released by Joeboy on Tuesday March 07, 2017 @10:47AM (#13811243)
I think it's sporadically refixed and rebroken.
Re:Firefox 52 released by baq on Tuesday March 07, 2017 @10:34AM (#13811084)
but doesn't it show something completely different, ie. DOM after JS ran?