Closed Bug 49968 Opened 24 years ago Closed 23 years ago

accesskey attribute of the 'Area' element tag fails.

Categories

(Core :: Layout, defect, P3)

Sun
Solaris
defect

Tracking

()

VERIFIED DUPLICATE of bug 81473
Future

People

(Reporter: nasiruddin.shaikh, Assigned: joki)

References

()

Details

(Keywords: access, html4, Whiteboard: suntrak-n6)

Pressing alt + accesskey doesn't highlight the area.
Dividing up claytons bugs to triage.
Assignee: clayton → dcone
Triage of Clayton bugs.
Assignee: dcone → joki
massive update for QA contact.
QA Contact: petersen → lorca
Could we get some QA help on these bugs, please?  A first cut analysis of 
whether they occur Mac/Windows/Linux would be a big help in figuring out their 
priority.  Thanks.
Keywords: qawanted
Marking as Duplicate of #959-if you disagree, let me know.


*** This bug has been marked as a duplicate of 959 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Sorry about that.  After being slapped upside the head, reopening bug and closing 
959.  The difference is that 959 was a "Not Implemented Yet" bug, whereas this is 
a "Not Working At All" bug.  Any other bugs stemming from that should be opened 
separately-it was getting out of control.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
We have a lot of problems with imagemap areas.  Unfortunately it doesn't look 
like any of them will get fixed for this release.  Marking future.
Target Milestone: --- → Future
Um, what??

Hixie: any thoughts? I think this is problematic, ctrl and alt b are both 
assigned (bookmarks: menu/management).
xul2-d goes to debug
xul-a goes to selectall
xul-c goes to copy

Assuming this is spec and we're trying to do it [Hixie if this isn't, stop me 
now]
I think that in order to do this we'd need an F6 "unbind chrome" that would 
change the window's appearance (title?) to indicate that chrome bindings are 
not bound. While in this state, mozilla could try to give accesskeys to html. 
Pressing F6 [or maybe escape?] would restore chrome bindings and disable this 
html stuff.

Personally unless i'm given fair warning I expect that all key presses be 
managed by my app('s chrome), not some web page.
Whiteboard: suntrak-n6
Small but very important question, is this hard to implement? Now they work for
links already!
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
qa contact updated.
QA Contact: gerardok → bsharma
This occurs on windows also.  win32 (build 2001040904)
SPAM. HTML Element component is deprecated, changing to Layout component. See
bug 88132 for details.
Come on Bugzilla, you can do it...
Component: HTML Element → Layout
cc'ing aaronl.
Keywords: html4
QA Contact: bsharma → moied

*** This bug has been marked as a duplicate of 81473 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago23 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.