Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 82482 DNS pre-resolution was disabled in Webkit
Starred by 2 users Project Member Reported by jar@chromium.org, May 12, 2011 Back to list
Status: Fixed
Owner: abarth@chromium.org
Closed: May 2011
Cc: jar@chromium.org
Components:
OS: ----
Pri: 1
Type: Bug

Restricted
  • Only users with EditIssue permission may comment.


Sign in to add a comment
A change in webkit Settings.cpp created a default setting of "false" for m_dnsPrefetchingEnabled(), which in turn disabled all of DNS resolution.

What is the expected result?

a) Clear your DNS results by visiting a incognito window, and then closing it.
b) visit about:dns  (and you'll see almost no resolutions.
c) go to another tab, and do a search on google.
d) Wait until the search results render.
e) go back to about:dns tab, and refresh.  You should see a LOT of host names resolved


What happens instead?

Step (e) shows no pre-resolution performed when we load (and scan) a page.

This setting also blocks mouse-over pre-resolution, and link rel=dns-prefetch based resolution (both of which should work when this is repaired.


Note that this bug did not block pre-resolution of sub-resources, which was done without webkit interactions.

I'm only labeling this P1 because it was a large feature regression.  It is blocking work by vendors to implement/test/deploy improved page and advertisement handling (that was where I got the report).


UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.30 Safari/534.30



 
Comment 1 by abarth@chromium.org, May 12, 2011
Step 1 of the fix is https://bugs.webkit.org/show_bug.cgi?id=60736
Comment 2 by k...@google.com, May 13, 2011
Labels: Mstone-12 ApprovedForMerge
Comment 3 by jar@chromium.org, May 13, 2011
Just to clarify: The approve to merge is for the one-line fix, changing the default value from "false" to "true" in our webkit branch for Chrome 12.
Comment 4 by abarth@chromium.org, May 16, 2011
Status: Fixed
Fixenated in http://codereview.chromium.org/7021008/
Project Member Comment 5 by bugdroid1@chromium.org, Oct 13, 2012
Labels: Restrict-AddIssueComment-Commit
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.
Project Member Comment 6 by bugdroid1@chromium.org, Mar 10, 2013
Labels: -Area-WebKit -Mstone-12 Cr-Content M-12
Project Member Comment 7 by bugdroid1@chromium.org, Mar 13, 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member Comment 8 by bugdroid1@chromium.org, Apr 6, 2013
Labels: -Cr-Content Cr-Blink
Sign in to add a comment