[RFE]<applet>. focus() doesn't exist (supported by IE)

RESOLVED EXPIRED

Status

()

Core
Plug-ins
--
enhancement
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Sean McLinden, Unassigned)

Tracking

(Depends on: 1 bug)

1.0 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; (R1 1.5); .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

This MAY be related to bug #268945 (where Javascripot typeof of type <applet> 
returns a function rather than an object, but there I get an error of the form:

document.applets."appletName".focus is not a function

when I attempt to set the focus on a applet. This does not happen in IE 
(unfortunately).

Reproducible: Always

Steps to Reproduce:
1. Embed an applet in an HTML page (I'm using Ekit)
2. Attempt to set the focus to the applet.
3.

Actual Results:  
Error (the focus() method is undefined)

Expected Results:  
Transferred the focus to the applet (in this case JTextEdit pane)

This would be less serious if the method were simply defined as a null method 
but because the focus call is embedded in a Javascript function, it breaks the 
page.
Not a security bug, clearing flag.

-->Core product, not firefox specific.

The DOM specs don't require focus() for HTMLAppletElement, HTMLEmebedElement, or
HTMLObjectElement objects. IE apparently supports it, maybe we want to in quirks
mode or something. --> enhancement.
Assignee: firefox → nobody
Group: security
Severity: major → enhancement
Component: General → Plug-ins
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → plugins
Hardware: PC → All
Summary: <applet> focus() is not a function → [RFE]<applet>. focus() doesn't exist (supported by IE)
Version: unspecified → 1.0 Branch
There would be some accessibility problem if we don't support this feature, see
http://www.warp.webaim.org/resource/Resource.php?assetId=2

<blockquote>
Those using Mozilla, Netscape 7, or Opera will notice that the Flash content is
skipped entirely when navigating with the Tab key (or Q and A keys in Opera). To
access the elements within the Flash movie with these browsers, the user must
use the mouse to click within the movie. At this point, you will then no longer
be able to navigate outside of the Flash movie without using the mouse. This can
be an issue for people with motor disabilities that must use the keyboard for
navigation.
</blockquote>

Can someone confirem this to NEW?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.