RESOLVED FIXED72713
Opening Web Inspector for non-html content
https://bugs.webkit.org/show_bug.cgi?id=72713
Summary Opening Web Inspector for non-html content
Jaakko Holster
Reported 2011-11-18 04:01:27 PST
Web Inspector cannot be opened when the current document is not web page (ie. not text/html). In that case the menu item is disabled and the keyboard shortcut works neither. However, if you open Web Inspector before opening non-html page, Web Inspector keeps open and works fine (ie. shows request related info etc). Because clearly Web Inspector works and can be useful with other content types than html, it should be not prevented to open Web Inspector for non-html content. Demonstration: 1) Go to http://www.google.com/robots.txt (non-html content) 2) Web Inspector can *not* be opened 3) Go to http://google.com (html content) 4) Open Web Inspector 5) Now go to previous url (http://www.google.com/robots.txt) 6) Web Inspector stays visible and can be used
Attachments
sam
Comment 1 2012-05-03 03:05:06 PDT
(In reply to comment #0) > Web Inspector cannot be opened when the current document is not web page (ie. not text/html). In that case the menu item is disabled and the keyboard shortcut works neither. > > However, if you open Web Inspector before opening non-html page, Web Inspector keeps open and works fine (ie. shows request related info etc). Because clearly Web Inspector works and can be useful with other content types than html, it should be not prevented to open Web Inspector for non-html content. > > Demonstration: > > 1) Go to http://www.google.com/robots.txt (non-html content) > 2) Web Inspector can *not* be opened > 3) Go to http://google.com (html content) > 4) Open Web Inspector > 5) Now go to previous url (http://www.google.com/robots.txt) > 6) Web Inspector stays visible and can be used I have tried it with my chrome and qt, but inspector shows up properly. Is it still an issue?
Jaakko Holster
Comment 2 2012-05-03 03:29:34 PDT
> I have tried it with my chrome and qt, but inspector shows up properly. Is it still an issue? Still an issue with the latest Safari (5.1.5).
Note You need to log in before you can comment on or make changes to this bug.