4 ms·

Doesn't mention if the major problem I have with Firefox 51 is fixed. It makes a new, unauthenticated request every time I do View Source rather than showing th

by Joeboy 10y ago

Doesn't mention if the major problem I have with Firefox 51 is fixed. It makes a new, unauthenticated request every time I do View Source rather than showing the source of the page I'm looking at, which is an extreme PITA. If View Source works properly, that'd be worth upgrading for immediately.

sp332 10y ago
That is annoying, but does the Inspector in the Developer Tools show what you're looking for?
- baq 10y ago
  but doesn't it show something completely different, ie. DOM after JS ran?
- Joeboy 10y ago
  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.
  - Drdrdrq 10y ago
    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?
- rpeden 10y ago
  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 https://bugzilla.mozilla.org/show_bug.cgi?id=307089
  - Joeboy 10y ago
    I think it's sporadically refixed and rebroken.
Etzos 10y ago
This is the way it should be in every browser, actually. View source (as in the raw non-corrected source) can take up a considerable amount of space since it's only ever needed when someone is viewing the source. Otherwise the "source" gets transformed internally to be compliant with what the browser can understand and render. Unless you were talking about some other kind of view source?
- Joeboy 10y ago
  The problem I have right now is that when I view the source of a page I'm working on, I get the source of the login page instead. I don't think that is justifiable behaviour.
  - yazaddaruvala 10y ago
    #spaproblems
    - Joeboy 10y ago
      It's not a spa, these are #websitewithloginproblems.
      - yazaddaruvala 10y ago
        That is surprising, that would imply that view-source isn't using the same cookies as the regular browsing experience. Which seems like a bug.
      - Forlien 10y ago
        This seems strange. If you view page source on this comments page while logged in to Hacker News, does the source show you as not logged in? When I do that, my source contains the link to my profile (user?id=Forlien) at the top so I know it's giving me the logged-in version.
        Joeboy 10y ago
jxelam 10y ago
Does it not work to select all, right click and "view selection source"?
- Joeboy 10y ago
  I think that gets the post-js version of the page, although I'm not 100% sure.
  - jxelam 10y ago
    Yes I think you're right. Although the post-js version would be the page you're looking at, so it makes sense it'd prioritise that over "what html was sent from the server which may not reflect what you're seeing".
bzbarsky 10y ago
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.
- mconley 10y ago
  Please cc me too. (mconley at mozilla dot com)
  - Joeboy 10y ago
    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.
    - mconley 10y ago
      All good. Thanks for checking. :)
    - nnethercote 10y ago
      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-fix/Refresh-Firefox-reset-add-ons-and-settings/ta-p/23405 https://support.mozilla.org/t5/Procedures-to-diagnose-and-fi...
    - bzbarsky 10y ago
      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...
bigbugbag 10y ago
Even better would be to have the possibility to edit said source from cache and see the result as was possible with opera until it kicked out its founder to become a google chrome skin and focus on quarterly profits.

by Joeboy 10y ago

sp332 10y ago

That is annoying, but does the Inspector in the Developer Tools show what you're looking for?

baq 10y ago
but doesn't it show something completely different, ie. DOM after JS ran?
Joeboy 10y ago
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.
- Drdrdrq 10y ago
  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?
rpeden 10y ago
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 https://bugzilla.mozilla.org/show_bug.cgi?id=307089
- Joeboy 10y ago
  I think it's sporadically refixed and rebroken.

Etzos 10y ago

This is the way it should be in every browser, actually. View source (as in the raw non-corrected source) can take up a considerable amount of space since it's only ever needed when someone is viewing the source. Otherwise the "source" gets transformed internally to be compliant with what the browser can understand and render. Unless you were talking about some other kind of view source?

Joeboy 10y ago
The problem I have right now is that when I view the source of a page I'm working on, I get the source of the login page instead. I don't think that is justifiable behaviour.
- yazaddaruvala 10y ago
  #spaproblems
  - Joeboy 10y ago
    It's not a spa, these are #websitewithloginproblems.
    - yazaddaruvala 10y ago
      That is surprising, that would imply that view-source isn't using the same cookies as the regular browsing experience. Which seems like a bug.
    - Forlien 10y ago
      This seems strange. If you view page source on this comments page while logged in to Hacker News, does the source show you as not logged in? When I do that, my source contains the link to my profile (user?id=Forlien) at the top so I know it's giving me the logged-in version.
      - Joeboy 10y ago

jxelam 10y ago

Does it not work to select all, right click and "view selection source"?

Joeboy 10y ago
I think that gets the post-js version of the page, although I'm not 100% sure.
- jxelam 10y ago
  Yes I think you're right. Although the post-js version would be the page you're looking at, so it makes sense it'd prioritise that over "what html was sent from the server which may not reflect what you're seeing".

bzbarsky 10y ago

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.

mconley 10y ago
Please cc me too. (mconley at mozilla dot com)
- Joeboy 10y ago
  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.
  - mconley 10y ago
    All good. Thanks for checking. :)
  - nnethercote 10y ago
    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-fix/Refresh-Firefox-reset-add-ons-and-settings/ta-p/23405 https://support.mozilla.org/t5/Procedures-to-diagnose-and-fi...
  - bzbarsky 10y ago
    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...

bigbugbag 10y ago

Even better would be to have the possibility to edit said source from cache and see the result as was possible with opera until it kicked out its founder to become a google chrome skin and focus on quarterly profits.