Bug 17574 – Acid2: Inspection fails after internal anchor navigation

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Robert Blaut]

Summary: During digging into bug 4911 I found that the Acid2 test is impossible to inspect with Web Inspector on the first load. The Web Inspector opens window but without html code in it.

Steps to reproduce:
1) Go to a page: http://hixie.ch/tests/evil/acid/002/#top
2) Click "Take the Acid2 test"
3) Right click on "Hello World" an choose Inspect element

Expected result:
The opened window should have html code in it.

Current result:
The opened window is blank.

The problem disappears after reloading the page and retrying above procedure. Notice also incorrect layout!

[Adam Roben (:aroben)]

Works fine here. You may have run into the bug where the Inspector is blank if you turn on WebKitDeveloperExtras and then open the Inspector without loading a new page <rdar://5667892>.

Robert, do you think this is the case? If so, we should retitle this bug and make it the Bugzilla equivalent of <rdar://5667892>.

[Robert Blaut]

(In reply to comment #1)
> Robert, do you think this is the case? If so, we should retitle this bug and
> make it the Bugzilla equivalent of <rdar://5667892>.
> 

No, it isn't the case you described. Sad to say but in the first step above I typed wrong URL. The exact steps should be:

1) Go to a page: http://hixie.ch/tests/evil/acid/002/
2) Click "Take the Acid2 test"
3) Right click on "Hello World" an choose Inspect element

The second step is crucial for this issue. The issue isn't visible if you perform these steps:

1) Go to a page: http://hixie.ch/tests/evil/acid/002/#top
2) Right click on "Hello World" an choose Inspect element.

[Cameron Zwarich (cpst)]

This also works with the standard data URI version of the test:

http://www.webstandards.org/files/acid2/test.html

[Cameron Zwarich (cpst)]

Created attachment 19988 [details]
Reduction

Here is a reduction. It is essentially the same reduction as for bug 13693. It seems the internal anchor navigation causes the inspector to attempt to inspect the 404 in the embedded object element.

[Cameron Zwarich (cpst)]

Created attachment 19991 [details]
Another test case

It has nothing to do with failure to load in the object element, as can be seen in this example. Clicking then inspecting the page causes http://www.webkit.org/ to be inspected instead.

[Cameron Zwarich (cpst)]

Created attachment 19998 [details]
Further reduction

The main document appears in the inspector, except it has type Other. Here is a further reduction without the 404 that illustrates the problem alone.

This is occurring because

CachedResource* cachedResource = frame->document()->docLoader()->cachedResource(requestURL.string());

in InspectorResource::type() is null. If I change the subsequent test to return Doc instead of Other, then inspection works fine.

I think this is actually a loader issue, because it should be a cached resource, unless my definition of cached resource is skewed.

[Robert Blaut]

I'm no longer able to reproduce the problem in WebKit r35177. I close the bug report.