Closed
Bug 168106
Opened 23 years ago
Closed 20 years ago
shouldn't emit caret-move event when caret position was actually not changed
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: yuanyi21, Assigned: yuanyi21)
References
(Depends on 1 open bug)
Details
(Whiteboard: sunport17)
Attachments
(1 file, 1 obsolete file)
3.69 KB,
patch
|
Details | Diff | Splinter Review |
Currently, If i am on first position of the text and I press left arrow,
"text-caret-moved" event is emited even the cursor position is the same. Same
thing for right arrow, home, end.
Comment 2•23 years ago
|
||
Kyle, it looks good. Will you do this same thing for the MSAA part? I've been
wanting to fix that for the Windows code as well.
Comment 3•23 years ago
|
||
Actually, I just realized this must really be a problem with our selection
listener code.
Isn't the correct way to fix this to make that code not send selection changed
events when it hasn't really changed?
FYI: The bogus selection changed notifications problem was filed as bug 140303.
aaron, since there is no any progress in bug 140303 for a couple of months, I
would like to fix this problem here as a workaround. Then we can remove this
temporary fix after bug 140303 get fixed. This fix is helpful for our *nix
accessibility project.
Attachment #99033 -
Attachment is obsolete: true
Updated•21 years ago
|
Whiteboard: sunport17
Updated•20 years ago
|
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•