Closed
Bug 301621
Opened 19 years ago
Closed 17 years ago
Expose elements with onclick from addEventListener()
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(3 files, 3 obsolete files)
508 bytes,
text/html
|
Details | |
8.09 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
3.12 KB,
patch
|
ginnchen+exoracle
:
review+
|
Details | Diff | Splinter Review |
We now expose elements with onclick handlers added declaratively via an onclick attribute, but we do not yet expose elements whose onclick was put there via addEventListener() in a script. We should expose those as well.
Assignee | ||
Comment 1•17 years ago
|
||
Assignee | ||
Comment 2•17 years ago
|
||
Assignee | ||
Comment 3•17 years ago
|
||
Assignee | ||
Updated•17 years ago
|
Attachment #263775 -
Attachment is obsolete: true
Assignee | ||
Updated•17 years ago
|
Attachment #263776 -
Attachment is obsolete: true
Assignee | ||
Comment 4•17 years ago
|
||
Assignee | ||
Comment 5•17 years ago
|
||
Attachment #263778 -
Attachment is obsolete: true
Attachment #263816 -
Flags: review?
Assignee | ||
Updated•17 years ago
|
Attachment #263816 -
Flags: review? → review?(Olli.Pettay)
Comment 6•17 years ago
|
||
Comment on attachment 263816 [details] [diff] [review] Use new nsIEventListenerManager::HasListenersFor() API instead of checking onclick attibute >+ >+PRBool nsAccessibilityUtils::HasListener(nsIContent *aContent, const nsAString& aEventType) >+{ >+ nsCOMPtr<nsPIDOMEventTarget> eventTarget(do_QueryInterface(aContent)); >+ if (!eventTarget) { >+ return PR_FALSE; >+ } nsIContent is nsPIDOMEventTarget so no need to QI. (Not sure if you need null check still)
Attachment #263816 -
Flags: review?(Olli.Pettay) → review+
Assignee | ||
Comment 7•17 years ago
|
||
Checked in with QI removal. Thanks for the tip.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Flags: in-testsuite?
Assignee | ||
Comment 8•17 years ago
|
||
This doesn't work for <li> elements with an onclick.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•17 years ago
|
||
Also removes unnecessary line that clears focusable state on list. The focusable state is now handled correctly in nsAccessible::GetState(), and technically anything can be focusable now, because of tabindex.
Attachment #265705 -
Flags: review?(ginn.chen)
Attachment #265705 -
Flags: review?(ginn.chen) → review+
Assignee | ||
Updated•17 years ago
|
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•17 years ago
|
||
Tim mentioned that on a site like CNN he is seeing far more onclicks in the virtual buffer than he does with IE and a screen reader.
You need to log in
before you can comment on or make changes to this bug.
Description
•