Closed
Bug 649284
Opened 14 years ago
Closed 8 years ago
Invalid position of caret in MSAA event 'EVENT_OBJECT_LOCATIONCHANGE' (only if menubar is displayed)
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gregory.wulff, Unassigned, NeedInfo)
References
(Blocks 2 open bugs)
Details
(Keywords: access)
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
With activated menubar the coordinates of the caret are invalid while getting the MSAA EVENT_OBJECT_LOCATIONCHANGE event.
Reproducible: Always
Steps to Reproduce:
1.Display menubar of firefox
2.Run Microsoft's MSAA Inspector (inspect32.exe) and check "Watch caret" and "Show caret highlight" Buttons in Toolbar
3.Klick within any edit field of any webpage and type.
Actual Results:
Caret highlight is always beyond the real caret position (means that EVENT_OBJECT_LOCATIONCHANGE gives the wrong position)
Expected Results:
Caret highlight should be at the position of the real caret
Reporter | ||
Comment 1•14 years ago
|
||
Occurs with all windowsversions, tested Win XP and Win7
Version: unspecified → 4.0 Branch
Updated•14 years ago
|
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
QA Contact: disability.access → accessibility-apis
Version: 4.0 Branch → 2.0 Branch
Reporter | ||
Comment 2•14 years ago
|
||
Occurs only in FF 4.0, in FF 3.6 (and lesser) it worked correctly
Updated•13 years ago
|
Blocks: caretsela11y, a11ynext
Keywords: access
Comment 3•8 years ago
|
||
Hi Gregory, is this still an issue in a current Firefox version?
Flags: needinfo?(gregory.wulff)
Reporter | ||
Comment 4•8 years ago
|
||
Hi Marco,
no. I just tested with FF 49.0 and the problem seems to be fixed. Thanks.
Reporter | ||
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Reporter | ||
Updated•8 years ago
|
Resolution: INVALID → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•