Closed
Bug 285581
Opened 20 years ago
Closed 6 years ago
unable to reload page using F5 when disabled element has focus
Categories
(Firefox :: Keyboard Navigation, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jepsar, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: testcase)
Attachments
(1 file)
406 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
I'm working on a page with "previous" and "next" <button>'s on it to browse
through <div>'s on a page (javascript: style.display = 'block'|'hidden'). On the
last page I disable the "next" <button> (javascript: disabled = 'disabled'). In
this situation the disabled <button> has focus and I can't use some (all?) key
shortcuts like F5.
If needed I can put a test page online tonight.
Reproducible: Always
Steps to Reproduce:
See details
Actual Results:
See details
Expected Results:
See details
Comment 1•20 years ago
|
||
Yes, please attach a testcase (by using Create a New Attachment) or put a
testcase somewhere online.
Also try testing with the latest nightly trunk build:
http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/
Reporter | ||
Comment 2•20 years ago
|
||
I've also tested this with the 10-Mar-2005 17:03 trunk build
Reporter | ||
Comment 3•20 years ago
|
||
Maybe the button should loose focus when disabled by javascript
Comment 4•20 years ago
|
||
I think another bug is that the disabled element should not have focus at that
point. When that would be fixed, it probably would also fix your bug.
Comment 5•20 years ago
|
||
In fact we always need to move the focus if an element, or an ancestor to an
element is disabled, hidden or destroyed.
This should be done at the most general level possible so that it benefits not
just HTML, but also XUL and everything else.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050329 Firefox/1.0+
(In reply to comment #2)
> Created an attachment (id=177029) [edit]
> Bug example
Status -> NEW
FWIW Ctrl+F5 works. In fact, just pressing Ctrl, then F5 separately works too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•18 years ago
|
QA Contact: jruderman → keyboard.navigation
Comment 9•6 years ago
|
||
This seems to work for me with the latest Firefox nightly build. Please re-open if you can reproduce.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•