Removed the requirement to call setSelection directly on the text field in order to set its selecti…

Source/modules/accessibility/AXLayoutObject.cpp

Index: Source/modules/accessibility/AXLayoutObject.cpp
diff --git a/Source/modules/accessibility/AXLayoutObject.cpp b/Source/modules/accessibility/AXLayoutObject.cpp
index 2d4976431777b4cb7ea0fd4af4c52b03afaaccf5..8ee841a7ca03f3b7961a7204b6da929ca85eb5ef 100644
--- a/Source/modules/accessibility/AXLayoutObject.cpp
+++ b/Source/modules/accessibility/AXLayoutObject.cpp
@@ -2018,10 +2018,10 @@ void AXLayoutObject::setSelection(const AXRange& selection)
     AXObject* focusObject = selection.focusObject ?

[Peter Lundblad, 2015/08/28 15:09:43]

Perhaps the initial part of this function could be simplified if you did the
null->this assignments first and then do the rest of the checks on those
pointers. Now it looks like there is some duplication in there.

         selection.focusObject.get() : this;
 
-    if (anchorObject == this && anchorObject == focusObject
-        && layoutObject()->isTextControl()) {
+    if (anchorObject == focusObject
+        && anchorObject->layoutObject()->isTextControl()) {
         HTMLTextFormControlElement* textControl = toLayoutTextControl(
-            layoutObject())->textFormControlElement();
+            anchorObject->layoutObject())->textFormControlElement();
         textControl->setSelectionRange(selection.anchorOffset, selection.focusOffset,
             SelectionHasNoDirection, NotDispatchSelectEvent);

[Peter Lundblad, 2015/08/28 15:09:43]

Why doesn't the direction depend on which one of the start and end pint is
larger to keep the distinction between anchor and focus even for text fields?

         return;