On Tue, 20 Apr 2010 10:12:16 -0300 Gustavo Noronha Silva <k...@debian.org> wrote:
> I can reproduce the problem with the HTML page you crafted. Seems > worth reporting upstream (I will do it later today). > For some reason WebKit thinks it should do the pre-resolution when the > mouse is moved on top of the blank area of the page indeed. Just to clarify: -- with the test HTML page, do you get the DNS query storm only when the mouse is over the <http://./> links, or also over the non-link areas of the page? -- if it happens on the non-link areas, is that true only for the test page, or also for any random web page, for example <http://www.debian.org/>? -- if it happens for just about any web page, why do you suppose that the other two investigators can't reproduce it? Does it have something to do with the hostname resolver configuration, as I suggested above? -- why would the behavior disappear when the same page is referenced with a <file://> rather than a <http://> URL? I note the following item in your backtrace, which may reveal where and how this bug was introduced: #2 0x00007f0f1d4bc740 in WebCore::Chrome::mouseDidMoveOverElement ( this=0x7f0f204da270, result=..., modifierFlags=24594032) at ../WebCore/page/Chrome.cpp:340 (The "Chrome" label is probably significant.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
