User-Agent: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre) Gecko/20100802 Minefield/4.0b3pre Build Identifier: When selecting 'View Source' the page should be displayed in a tab rather than a new window. Reproducible: Always

Aaron, that bug is for Thunderbird, this is for Firefox. Unconfirming as this was a request for Firefox 4, being as View Source is available via the Developer Menu.

Matthias, the two bugs aren't the same. bug 454336 is about the _option_ to middle click this one is about opening in a tab by default.

This is not worth it for web developers - It would add more hassle for them when debugging and creating websites. Its nice to both in together, not a page in one tab and the source in a background tab. It should be WONTFIX.

Web Devs don't make up the majority of users though and for said devs, I'm sure there'd be an extension to open up the page in a new window. Personally I can only think of one or two examples when I've needed to view the source at the same time as the web page.

(In reply to comment #6) > Web Devs don't make up the majority of users though and for said devs, I'm sure > there'd be an extension to open up the page in a new window. Web developers are probably the only ones who want to view the source of a website. If we agree that web developers want new windows, this enhancement request seems invalid.

(In reply to comment #7) > (In reply to comment #6) > > Web Devs don't make up the majority of users though and for said devs, I'm sure > > there'd be an extension to open up the page in a new window. > > Web developers are probably the only ones who want to view the source of a > website. If we agree that web developers want new windows, this enhancement > request seems invalid. It'(In reply to comment #7) > (In reply to comment #6) > > Web Devs don't make up the majority of users though and for said devs, I'm sure > > there'd be an extension to open up the page in a new window. > > Web developers are probably the only ones who want to view the source of a > website. If we agree that web developers want new windows, this enhancement > request seems invalid. It's absolutely possible that this is invalid, but I really don't think so. A quick Google provides more than enough ways to achieve this, including finding a previous project page that I hadn't seen before. https://wiki.mozilla.org/Firefox/Projects/View_Source_in_Tab https://addons.mozilla.org/en-US/firefox/addon/13029/ https://addons.mozilla.org/en-US/firefox/addon/151809/ https://addons.mozilla.org/en-US/firefox/addon/5908/ At the moment, this is a window, that makes it harder to find on computers with a high volume of tabs should you click away. And with the advances in in-content UI, we're more than equipped to do this. The argument that people may want to see the web page and the source at the same time is a fair one, but most web devs needing to see a page and edit, will undoubtedly be using something they can edit, rather just viewing the source. I personally believe this is the natural evolution of view source. Displayed in a tab, next to the web page.

I think you run the risk of making View source annoying to use then functional as it is by doing so. We just don't want to make a change for the sake of making everything a tab. It should be function first, and nightly testers are a minority of users, to say that we should change it because we can, doesn't have any basis to go on.

I think this would good to get a test pilot study going on this if we really think its an issue to change it.

(In reply to comment #9) > I think you run the risk of making View source annoying to use then functional > as it is by doing so. What is the function you believe view source has?

(In reply to comment #11) > (In reply to comment #9) > > I think you run the risk of making View source annoying to use then functional > > as it is by doing so. > > What is the function you believe view source has? I answered this in a previous comment.

I'm asking you to clarify.

(In reply to comment #13) > I'm asking you to clarify. Page source is the first line of defense for people who need to debug or look at websource. And if its in a background tab, your not going to be able to see it side by side where its most effective unless you put them in two windows which defeats the purpose of doing them in tabs. No user would open up a ton of tabs and a ton of view source windows. Having them in tabs won't keep you anymore organized then the taskbar does. Then when you play with webpages you cannot look at the source together.. so you have to have them side by side anyway. Only people who do this for a living really understand its value.

(In reply to comment #14) Realistically speaking, when do you ever have to view source and page side by side? Surely keeping content neatly filed side by side should be a priority? Whether we agree or not (I at least do), there has been a UX Team goal to reduce the number of Windows used in a session, this proposal adheres to that.

Any tab can be dragged to a separate window, and just like we have suggested for Downloads, the bookmarks windows, etc — we should remember if you did this, and keep it as a separate window the next time you open it. But I agree, it should open in a tab by default.

I know Chrome does it in a tab, which maybe is ok, but I don't want to lose the functionality too. There currently is no page source functionality if you click on source code from a current tab. We should keep access to and make sure the work in a tab too: Text Size <-- probably is just renamed Zoom Menu Wrap Long Lines Syntax Highlighting

(In reply to comment #17) > I know Chrome does it in a tab, which maybe is ok, but I don't want to lose the > functionality too. There currently is no page source functionality if you > click on source code from a current tab. > > We should keep access to and make sure the work in a tab too: > Text Size <-- probably is just renamed Zoom Menu > Wrap Long Lines > Syntax Highlighting It's been stated it'll appear in a tab by default and if you detach it, it'll stay detached as a pref.

Does not block bug 696526, in my opinion. And actually, I prefer the source in a window, as it is now, than in a tab. Typically I have many tabs open : long term browsing. For a given tab, I want to view something in the source : short term operation. I don't want the source to be mixed with my tabs, I prefer to have it as a window above the rest : I look at what I want, and then I close it, and my tabs haven't been touched. Remember that there are a bunch of scenarios in Firefox tab behaviour where closing a tab does not bring you in the tab you were in just just before. In addition, you typically compare the source with the rendered stuff...

Same as bug 103622 though that is in SeaMonkey at this time.

Is there any progress on this one? By now Firefox is the only browser not offering it in a tab. Chrome, Safari, Opera, .. do :(

(In reply to Leo Unglaub from comment #22) > Is there any progress on this one? You must mean regress. With the source in a new tab, how could I see the source and the page at the same time ? By detaching the tab to a new window... and then making sure that then the first page is back the active in the original window. That is : doing manually what Firefox does today. In Safari, I have the page source in a new window.