Issue metadata
Sign in to add a comment
|
AXPlatformNodeMac should support multiline labels for parameterised attributes |
||||||||||||||||||||||
Issue descriptionChrome Version : 62.0.3174.0 OS Version: OS X 10.13 Per Issue 743289, High Sierra has started asking for parameterised attributes on ui::AX_ROLE_STATIC_TEXT roles. AXPlatformNodeMac gives correct results for single-line labels. However, it could previously assume that it would be backed by a views::Textfield, which is currently only single-line. So it will return incorrect results for mutli-line views::Labels.
,
Jan 25 2018
,
Feb 6 2018
This looks like it would involve actually implementing [AXPlatformNodeMac AXLineForIndex] and changing [AXPlatformNodeMac AXRangeForLine]. lgrey@, can you take a look at this? Thanks :)
,
Feb 8 2018
Some notes: - It's unclear how the OS supports this. In multi-line NSLabels, VO-l reads a single line ONLY if the label is in the process of being read. VO-up and VO-down ignore the lines. - This is implemented for web content as BrowserAccessibility::GetLineStartOffsets (https://cs.chromium.org/chromium/src/content/browser/accessibility/browser_accessibility.cc?type=cs&l=805) which takes advantage of the fact that each line is a separate object - The kLineBreaks (https://cs.chromium.org/chromium/src/ui/accessibility/ax_enums.mojom?type=cs&q=package:chromium&l=564) attribute can be used to implement this in Views but is currently slated for deprecation Current thinking per offline discussions is that this should not block MacViews Secondary UI launch.
,
Feb 12 2018
+ Accessibility folks re: kLineBreaks deprecation
,
Mar 23 2018
Mac triage: let's target this at M68.
,
Apr 13 2018
,
Apr 17 2018
,
Apr 25 2018
Pls mark the bug as fixed if CL is landed in trunk and nothing else is pending. Thank you.
,
Jun 20 2018
,
Jul 12
,
Jul 12
,
Jul 26
,
Aug 13
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tapted@chromium.org
, Dec 4 2017