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. It turns out that this bug was already reported OVER A YEAR AGO: https://bugs.webkit.org/show_bug.cgi?id=23846#c3 A fix was proposed over six months ago: https://bugs.webkit.org/show_bug.cgi?id=23846#c5 I don't understand why this fix hasn't been applied upstream. Even if you don't think this behaviour is a security problem, it's a big waste of CPU and network resources to issue a completely useless external DNS query for every mouse movement event -- that is, for every few pixels that the pointer moves. That is a ridiculously stupid thing to do. Gustavo, I draw your attention particularly to the following comments: https://bugs.webkit.org/show_bug.cgi?id=23846#c14 https://bugs.webkit.org/show_bug.cgi?id=23846#c19 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
