Closed
Bug 163834
Opened 22 years ago
Closed 22 years ago
Use correct Accessible object to fire event when text-caret moved and text-selection changed
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.2alpha
People
(Reporter: yuanyi21, Assigned: yuanyi21)
References
Details
Attachments
(1 file, 1 obsolete file)
|
1.74 KB,
patch
|
aaronlev
:
review+
bryner
:
superreview+
|
Details | Diff | Splinter Review |
Now we use nsCaretAccessible itself, it should be a object that supports
nsIAccessibleText interface.
mass change of QA, milestone, platform.
Status: NEW → ASSIGNED
QA Contact: dsirnapalli → mindy.liu
Target Milestone: --- → mozilla1.2alpha
|
||
Comment 3•22 years ago
|
||
Comment on attachment 96159 [details] [diff] [review]
catch the currect dom node in AttachNewSelectionListener
r=aaronl
Attachment #96159 -
Flags: review+
use nsISelection's focus node instead of a member variable to create the
accessible object.
Aaron, could you r= again?
Attachment #96159 -
Attachment is obsolete: true
|
|
||
Comment 5•22 years ago
|
||
Comment on attachment 96775 [details] [diff] [review]
better fix - use the focus node
r=aaronl
Attachment #96775 -
Flags: review+
|
||
Comment 6•22 years ago
|
||
Comment on attachment 96775 [details] [diff] [review]
better fix - use the focus node
sr=bryner, with one nit: prevailing style here seems to be that 1-line |if| and
|else| bodies don't have their own block.
Attachment #96775 -
Flags: superreview+
checked in!
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•