- This change makes sure we resolve URLs upon adding the to the UI. Then we treat them as absolute links in context menu, etc. - There is no need to override context menu for links anymore - system menu will do.
Created attachment 160336 [details] Patch
Comment on attachment 160336 [details] Patch Attachment 160336 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13604003 New failing tests: inspector/styles/styles-url-linkify.html inspector/elements/elements-panel-rewrite-href.html
Created attachment 160360 [details] Archive of layout-test-results from gce-cr-linux-03 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: gce-cr-linux-03 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.39-gcg-201203291735-x86_64-with-Ubuntu-10.04-lucid
Created attachment 160373 [details] Patch
Committed r126572: <http://trac.webkit.org/changeset/126572>
(In reply to comment #5) > Committed r126572: <http://trac.webkit.org/changeset/126572> It broke a test at least on Qt: --- /ramdisk/qt-linux-64-release/build/layout-test-results/inspector/elements/iframe-load-event-expected.txt +++ /ramdisk/qt-linux-64-release/build/layout-test-results/inspector/elements/iframe-load-event-actual.txt @@ -1,6 +1,7 @@ Tests that iframe content is available after iframe's load event fired. See bug 76552. +error: Could not resolve DOM URL: resources/iframe-load-event-iframe-2.html After frame navigate @@ -25,6 +26,7 @@ </body> </html> </iframe> + - <div> </body> </html> Could you check it, please?
Looking...
(In reply to comment #7) > Looking... Fix landed as http://trac.webkit.org/changeset/126576.