Open
Bug 409000
Opened 18 years ago
Updated 3 years ago
Implement setActive() on elements
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: u81239, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2
Hi,
Firefox 3 implements the activeElement property, however the setActive() method is not available on DOM elements. In Internet Explorer, activeElement can be manipulated with focus() and setActive(), with slightly different semantics[1]. It would probably be good for Firefox to also implement the setActive() method, for completeness’ sake.
[1] http://msdn2.microsoft.com/en-us/library/ms533065.aspx
Martijn Wargers wrote on this subject:
> I think you should file a bug on this, for getting support for the
> setActive() method.
> From what I can read from the documentation and from testing, it
> focuses the element, but doesn't scroll the element into view (which
> is different from what .focus() does).
> Also, you can change the focused element inside a blurred window,
> without actually bringing that blurred window into front, so this
> really seems like a useful function to me.
> Please file a bug and CC me.
~Grauw
Reproducible: Always
The documentation for the setActive() method is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=409000
Comment 2•18 years ago
|
||
Example and explanation from msdn:
http://samples.msdn.microsoft.com/workshop/samples/author/dhtml/refs/setActive.htm
http://msdn2.microsoft.com/en-us/library/ms536738(VS.85).aspx
Comment 3•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
| Assignee | ||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•