Speculative fix for crash in WebAXObject::Markers

Even if this doesn't fix the vector out-of-bounds bug, which I think it would, it is certainly the correct way that AXNodeObject::Markers() should have been written in the first place.

Bug: 889746
Change-Id: Ib58c52213d719321eb975fb1070d83ccfa3cd376
TBR: dmazzoni@chromium.org, aboxhall@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/1277579
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599397}
1 file changed