[Webkit-unassigned] [Bug 15059] alert dialog in loop does not prevent cpu from spinning

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=15059





------- Comment #8 from shadow2531 at gmail.com  2007-08-23 17:01 PDT -------
(In reply to comment #7)
> Perhaps the CPU usage is coming from the pulsing OK button? Could you see if,
> for example, the Add Bookmark sheet causes the same issue? (Press Ctrl+D to get
> the sheet to appear)
> 

Just tried that and even tried just javascript:alert('test'); in the address
field. However, those won't reproduce the problem, but I can tell that the
flashing of the button uses a *tiny* bit of cpu.

However, I just narrowed it down.

page.html
<script>
alert('');
</script>

What that does is leave Safari in the loading state and while in the loading
state, waiting for the user to click O.K., Safari uses 100% cpu.

Now, I tried window.onload = function() { alert('');}; instead to wait till
after Safari was done loading the page so Safari wouldn't be left in the
loading state, but Safari still was.

So, this has nothing to do with a loop and a better description would be: when
Safari's in the loading state and an alert() pauses loading, it causes Safari
to use 100%.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.