After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 112636 - Can't break out of page with long alert sequence
Can't break out of page with long alert sequence
Status: RESOLVED WONTFIX
Product: galeon
Classification: Deprecated
Component: Mozilla interaction
1.3.4
Other Linux
: Normal normal
: ---
Assigned To: Philip Langdale
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2003-05-09 13:45 UTC by Mark Howard
Modified: 2011-02-14 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mark Howard 2003-05-09 13:45:30 UTC 
http://bugs.debian.org/190974 reports:
Go to this page:

http://www.mostannoyingwebpage.com/v1/

Click through the are you sure messages.

Galeon shows the alert sequence, but provides no apparent way to break
out of it by closing the tab or interrupting it etc.

This is more or less a DOS attack on the browser.  If I wanted to stop
it, it looks like I'd have to kill it and then tell it to lose the
restart history.

The browser's interface should be live during alerts, especially the tab
close buttons.
Comment 1 Mark Howard 2003-05-09 13:46:54 UTC 
Perhaps all javascript popups should have a "disable javascript" button?
Comment 2 Tommi Komulainen 2003-07-05 13:11:50 UTC 
Hmm, in mozilla it's possible to hit ESC quickly enough and it'll stop
the madness.  Won't work for us though :-/  I don't think we even know
when a given dialog is a javascript alert or some other dialog, like
the URL is invalid one...
Comment 3 Akhil Laddha 2011-02-14 13:05:50 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore.

Galeon developers won't be fixing or back porting any fixes for this version. Please upgrade to latest stable Galeon version to receive bug fixes.
We are sorry it could not be fixed for your version.