Bug 129266

Summary:

AX: findMatchingObjects backwards start position inconsistent with forwards start position when startObject == nullptr.

Product:

WebKit

Reporter:

Samuel White <samuel_white>

Component:

Accessibility

Assignee:

Samuel White <samuel_white>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

aboxhall, apinheiro, cfleizach, commit-queue, dmazzoni, jcraig, jdiggs, mario, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Mac (Intel)

OS:

OS X 10.9

Attachments:

Description	Flags
Patch.	none

Description Samuel White 2014-02-24 12:40:40 PST

If a search is done in the forward direction and no start object is specified, the very first child of the container is the first result candidate. However, if search is done in the reverse direction and no start object is specified, the container isn't even considered (basically negating the search). In this case we should start the search from the very last element in the container so the very last child of the container is the first result candidate.

Comment 1 Radar WebKit Bug Importer 2014-02-24 12:41:12 PST

<rdar://problem/16150888>

Comment 2 Samuel White 2014-02-24 14:33:47 PST

Created attachment 225098 [details]
Patch.

Comment 3 WebKit Commit Bot 2014-02-24 16:03:25 PST

Comment on attachment 225098 [details]
Patch.

Clearing flags on attachment: 225098

Committed r164615: <http://trac.webkit.org/changeset/164615>

Comment 4 WebKit Commit Bot 2014-02-24 16:03:28 PST

All reviewed patches have been landed.  Closing bug.