WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
114447
Remote Web Inspector doesn't work for some sites
https://bugs.webkit.org/show_bug.cgi?id=114447
Summary
Remote Web Inspector doesn't work for some sites
Tom Oakley
Reported
2013-04-11 08:53:38 PDT
Created
attachment 197593
[details]
The bug that appears in the Console when inspecting the Remote Web Inspector when a site does not work in the Remote Web Inspector Sometimes the Remote Web Inspector does not work for some sites, just displaying a blank white box where the DOM Tree should be. None of the assets/resources for that site load either (they are shown in the resources panel but just hang when trying a specific one). I have noticed that this seems to happen more on sites that are hosted locally, especially when using a port (i.e
http://localhost:1234
). I have been developing locally with Jekyll (
https://github.com/mojombo/jekyll
), which uses the port 4000 by default and this is one of the primary examples I have. When a site does not work, I have inspected the Web Inspector and the error is always the same:
http://cl.ly/OCyH
. I have tested this on an iPad 2 running iOS 6.1.3 and an iPhone 4S running iOS 6.1.3 and it is replaceable on both although occasionally the site will work, although it's often very slow and annoying.
Attachments
The bug that appears in the Console when inspecting the Remote Web Inspector when a site does not work in the Remote Web Inspector
(12.18 KB, image/png)
2013-04-11 08:53 PDT
,
Tom Oakley
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2013-04-11 08:53:49 PDT
<
rdar://problem/13630859
>
Tom Oakley
Comment 2
2013-04-11 08:55:30 PDT
The Webkit nightly revision number is
r148195
.
Joseph Pecoraro
Comment 3
2013-06-17 17:20:41 PDT
Oops, sorry this should have been fixed a while ago, ~4/18/2013.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug