New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 602455 link

Starred by 3 users
Status: Assigned
Owner:
█ nek...@chromium.org
Last visit > 30 days ago
Cc:
█ nek...@chromium.org
dmazz...@chromium.org
aboxhall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

AX: Selection fails for some cases involving soft line breaks

Project Member Reported by dtseng@chromium.org, Apr 11 2016 
- see the enclosed test:

https://codereview.chromium.org/1876243002/

The test tries to select every possible range within a static text node. The text itself contains several in line text boxes. The test times out waiting for a callback to (1, 0) (anchor offset, focus offset)


The test does pass if the markup is swapped with a less complex example.
Project Member

Comment 1 by bugdroid1@chromium.org, May 14 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9618f0ed66c582e8791fa6d37459056698ec1778

commit 9618f0ed66c582e8791fa6d37459056698ec1778
Author: dmazzoni <dmazzoni@chromium.org>
Date: Sat May 14 01:20:13 2016

Accessible setSelection function should use VisiblePositions

The accessible setSelection function tries to select text in the DOM based
on nodes and text offsets within the accessibility tree. However, this
was implemented assuming that the text offsets were Positions, but they
should actually be VisiblePositions, since typically redundant whitespace
is not displayed visibly and similarly not included in the accessible name
of text nodes.

BUG=602455

Review-Url: https://codereview.chromium.org/1942953003
Cr-Commit-Position: refs/heads/master@{#393722}

[add] https://crrev.com/9618f0ed66c582e8791fa6d37459056698ec1778/third_party/WebKit/LayoutTests/accessibility/set-selection-whitespace.html
[modify] https://crrev.com/9618f0ed66c582e8791fa6d37459056698ec1778/third_party/WebKit/Source/core/editing/EditingUtilities.h
[modify] https://crrev.com/9618f0ed66c582e8791fa6d37459056698ec1778/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp

Comment 2 by dmazz...@chromium.org, Mar 28 2017

Labels: NewComponent-Accessibility-Blink NewComponent-Accessibility

Comment 3 by dmazz...@chromium.org, Apr 21 2017

Components: Blink>Accessibility

Comment 4 by dmazz...@chromium.org, Apr 21 2017

Components: -UI>Accessibility
Labels: -newcomponent-accessibility-blink -newcomponent-accessibility

Comment 5 by dmazz...@chromium.org, Jul 27 2017

Labels: triage-aaron

Comment 6 by aleventhal@chromium.org, Aug 7 2017

Labels: -triage-aaron triage-nektar

Comment 7 by dmazz...@chromium.org, Aug 11 2017

Labels: triage-dougt

Comment 8 by dmazz...@chromium.org, Aug 11 2017

Labels: -triage-dougt
Project Member

Comment 9 by sheriffbot@chromium.org, Aug 13

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by dmazz...@chromium.org, Sep 14

Owner: nek...@chromium.org
Status: Assigned (was: Untriaged)
Nektarios, could you see if this is still an issue?
►

Sign in to add a comment