Bug 129266 - AX: findMatchingObjects backwards start position inconsistent with forwards start position when startObject == nullptr.
Summary: AX: findMatchingObjects backwards start position inconsistent with forwards s...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.9
: P2 Normal
Assignee: Samuel White
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2014-02-24 12:40 PST by Samuel White
Modified: 2014-02-24 16:03 PST (History)
9 users (show)

See Also:


Attachments
Patch. (5.73 KB, patch)
2014-02-24 14:33 PST, Samuel White
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
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.