[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 74569] [EL] [test case] submit confimation dialog appears
From:       Gérard Talbot <browserbugs () gtalbot ! org>
Date:       2011-08-31 0:18:33
Message-ID: E1QyYVl-0001Z6-Uc () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=74569


Gérard Talbot <browserbugs@gtalbot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |browserbugs@gtalbot.org




--- Comment #37 from Gérard Talbot <browserbugs gtalbot org>  2011-08-31 00:18:32 ---
Is this bug still happening, active?

I have not read the whole bunch of comments but this code

<FORM NAME="search" ACTION="action" METHOD="GET">
   <INPUT TYPE="text" SIZE=15
onKeyPress="if(event.which==13) {document.search.submit()}">
   <INPUT TYPE="submit" VALUE="BOOM">
 </FORM>

may well indeed (and rightly so) trigger a submit confimation dialog to appear
twice. The submit() invokation may trigger the onsubmit event handler in some
browsers and may *_not_* trigger it (or not correctly) in others.

onKeyPress="if(event.which==13) {document.search.submit();}

The possibly only single reason why this code may seem popular is because of an
IE6, IE7 and IE8 bug which I reported myself a few years ago:

http://www.gtalbot.org/BrowserBugsSection/MSIE8Bugs/#bug204
Submit button value not posted with form submission 
http://www.gtalbot.org/BrowserBugsSection/MSIE8Bugs/not-submitting-submit-value.html

The bug has been fixed in IE9 PP5 (beta 1) according to the_dees:
See bug #134 in 
http://the-dees.webs.com/iepp1/

------------

(In reply to comment #34)
> Changed severity to "crash".

Regarding the subsequent crash after closing the 2nd confirmation modal window,
that is in fact another clearly distinct, clearly separate bug. The system, it
seems, is not able to handle running into multiple modal windows (alert,
prompt, debug when having JS debugger on/active on errors) by stopping js
execution accordingly.

There are at least 2 other bug reports to that effect:

bug 279605: Opening javascript debugger hangs the application (CPU %tage
activity remains, stays high)

bug 278067: multiple firing of alert dialog cause reproducible application
crashes

-----------

I do not understand why people file bug reports but do not answer/reply back
when asked if the bug (this one has 75 votes!) is fixed or is still happening.

regards, Gérard

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konq-bugs mailing list
Konq-bugs@kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs

[prev in list] [next in list] [prev in thread] [next in thread]