When 'mailto:' is called using location.href in javascript, gifs stop animating.

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
12 years ago
11 years ago

People

(Reporter: Brad O'Farrell, Unassigned)

Tracking

1.5.0.x Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: CLOSEME 06/27, URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

When I make a call to "mailto:" by changing the value of "location.href" in Javascript, all gifs on the page stop animating. I need to use location.href because the content of the 'mailto:' is dependant on instance variables. The problem doesn't happen if I call "mailto:" using an anchor.

<A href="mailto:bradofarrell@gmail.com">Link</a> -- Will not cause the gifs to stop animating.

location.href="mailto:bradofarrell@gmail.com" -- <I>Will</I> cause gifs to stop animating.

An error does not show up in the JS console. I've tried it in Internet Explorer and do not get the same problem. I'm using Windows XP, but someone else tested it on Linux (using Firefox) and had the same problem.

Reproducible: Always

Steps to Reproduce:
Execute location.href="mailto:"; in JavaScript
Actual Results:  
Gifs stop animating.


Expected Results:  
The email client should open, and the page should be unaffected. 

This doesn't happen when it's called by setting the href with an anchor.
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
No response from reporter re: comment 1 -->INCOMPLETE.
Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.