Open Bug 299116 Opened 21 years ago Updated 12 days ago

treat mailto: links as popups (don't open except by explicit user action)

Categories

(Firefox :: File Handling, defect, P3)

x86
Windows XP
defect

Tracking

()

ASSIGNED

People

(Reporter: awburns, Assigned: emz)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.8) JavaScript allows you to set window.location="mailto:" . This will open a new mail window. If placed in a loop (especially infinite) this can result in a state where it is very hard to close the browser and stop the loop. The user is inundated with mail windows. This does appear to be a general problem for all major browsers. Reproducible: Always Steps to Reproduce: 1. Go to http://www.neodynium.com/display.php?id=61 2. Click on the link 'Click with Care' Actual Results: Multiple mailto: windows were opened. Expected Results: Don't know. May be considered to be correct functionality, but clearly there is a case for this being bad. You can call these mailto:'s in onload on a page, and they don't get treated like popups, so there is little a user could do on arriving at a page. I guess, ideally, they would be treated as popups.
Changing summary to make it clear this is not a request to eliminate mailto: entirely (which would be WONTFIXed) Might want to do it with all externally-opened links
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Firefox → Core
Summary: Javascript allows window.location="mailto:", and opens a new mail window → treat mailto: links as popups (don't open except by explicit user action)
Version: unspecified → Trunk
Also stop mailto in the meta refresh tags Steps to Reproduce: 1) http://ha.ckers.org/popup.html
*** Bug 322417 has been marked as a duplicate of this bug. ***
QA Contact: firefox → toolkit
Severity: normal → S3
Component: Security → File Handling
Priority: -- → P3
Product: Core → Firefox

We can require user activation (and consume it) for navigating to mailto. If there is no user activation we can fall back to the external protocol prompt that we show for other protocols.
Generally we should consider treating all general-purpose protocols (mailto, tel, irc, etc. = non vendor specifc) the same. Maybe that means making them all behave like mailto and not prompt when there is user activation.

Let's see how many tests this will break...
I'll take this as a side bug, so no promises on timeline.

Assignee: nobody → emz
Status: NEW → ASSIGNED
You need to log in before you can comment on or make changes to this bug.