https://issues.apache.org/ooo/show_bug.cgi?id=124363
Bug ID: 124363
Issue Type: DEFECT
Summary: Writer: Spelling errors not exposed semantically via
accessibility APIs
Product: General
Version: 4.1.0-dev
Hardware: All
OS: All
Status: CONFIRMED
Severity: minor
Priority: P3
Component: accessibility
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Blocks: 121767
Str:
1. Open a new document in Writer.
2. Ensure Writer is set up to do spell checking for English.
3. Type "My tset" (intentional typo, without quotes) and press space.
4. Obtain the accessible for the paragraph just entered.
5. Retrieve the text attributes for offset 3.
Expected: There should be an "invalid" attribute with a value of "spelling"
("invalid:spelling").
Actual: There is no "invalid" attribute. You can determine that there is a
spelling error because the CharUnderline attribute has a value of 10 (the WAVE
underline type).
This isn't a major issue because ATs *can* determine that there is a spelling
error. However, this is obscure at best. Ideally, this should be exposed
semantically, rather than relying on the way it is displayed.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
