We need to use the cached post response.

Add: Blocking  Issue 523 

Replacing labels:
   Area-BrowserBackend by Area-Internals

(No comment was entered for this change.)

Source does not matches viewed page: this means i need to use firefox for developing and chrome for browsing... until i decide that it is better use one browser only and I will drop the one that does not diplay source correctly :(

@manudear, real programmers don't need to debug :p

I'm a real programmer... or certainly not a virtual one in any case. I still need to debug... I too get annoyed by this bug, although as a way round it I either use Firefox View Source or use Chromes Inspect Element tool. Neither way is ideal though.

Debugging is for wimps. 


Just a joke ;)

http://www.gotwavs.com/0059305935/MP3S/Movies/Office_Space/mundanedetail.mp3

mundanedetail[1].mp3 219 KB   Download

This is the one issue that prevents me from using Chrome as a webdeveloper. Firefox gets it right!!

It's not just about inaccurate POST results (though that is also a huge problem) - it's having to wait for the entire page to reload a second time - whereas in every other browser the source opens up immediately. I understand the idea behind putting it into its own tab/thread and making it a "first-class citizen", but the reality is it doesn't need to be. I'm just looking at it once and closing it. I don't want it cluttering up my tab bar. It could just be dumped into a simple popup window and I think we all would be perfectly happy with that.

Thanks ahead of time for fixing this!

I agree with Andrew. It could either be put into a popup or into a new tab on the same thread as the original tab. The Web Developer Tools thing (Inspect Element) gets the source code as it is at the time of requesting (taking into account any effects that JavaScript may have had on it). I don't see why this would be a difficult thing to implement when a) other browsers already do this and b) the functionality is in use already but in a different way, if you see what I mean.

I "View Source" in browsers all the time (yes, as a dev), maybe to take a look at the doctype, the html used in general, or some specific part. Yes, that's what Inspect can be used for but sometimes you don't want to target an element, or wait for the inspector to load.
Also, as a young developer and web enthusiast, I would View Source regularly to learn about interesting things I came across. My brother has never been very techy but he's trying out HTML, and learning from others' source code is central to learning. It just seems that showing the source of the page presented is clearly the expected behaviour, and the most useful one.

While I appreciate that it's a concern mainly of developers, it causes me to wonder why there'd be a "View Page Source" menu item that acts unexpectedly at all? If "normal web users" don't use or care about the feature, then why would it be kept around in a form that's not useful to developers? Seems like half a solution for two groups. 

What if the issue is that a page is broken only in Chrome, or a feature of Chrome is broken when you're on specific page? You can see the errors and line numbers in the Javascript Console, but then you can't do anything with them, at least not in Chrome.

As I basically said in a similar post discussing essentially the same issue, the current state of the broken View Source page is an absolute deal breaker for web developers.

It just got fixed people, can someone edit the status please ?

Pavel was this fixed with  issue 523 ?

(No comment was entered for this change.)

Why does this item marked as fixed? It is NOT fixed AT ALL.
"view-source" still reloads whole page and fails badly for posts.
Can someone reopen it?

It *WAS* fixed, but they broke it again. My guess is that, having realized that the vast majority of Chrome users are developers, Google is trying to rectify the ratio by removing all developer-friendly features (read: open frame in new tab and "http:// in address bar - not to mention the ability to "open" a file by downloading it to a tmp directory). It's part of their new "policy of failure" (read: Buzz and Wave). Rock on guys!

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

(No comment was entered for this change.)