Set selection to INPUT/TEXTAREA before dispatching 'focus' event.

third_party/WebKit/LayoutTests/fast/forms/selection-functions.html

Index: third_party/WebKit/LayoutTests/fast/forms/selection-functions.html
diff --git a/third_party/WebKit/LayoutTests/fast/forms/selection-functions.html b/third_party/WebKit/LayoutTests/fast/forms/selection-functions.html
index e256af5e84b268fbe17fb4e2ac44d27f78542e1c..3b6bc3899ddfec8a4941c60f5e151a27cfe9a32d 100644
--- a/third_party/WebKit/LayoutTests/fast/forms/selection-functions.html
+++ b/third_party/WebKit/LayoutTests/fast/forms/selection-functions.html
@@ -88,6 +88,17 @@
                 elt.selectionEnd = 7;
                 display(elt);
                 
+                print("");
+                print("selectionStart and selectionEnd in focus handler:");
+                // Need to clear selection. Selection API calls above modified
+                // both of real selection and |elt|'s cached selection even
+                // though |elt| has no focus.
+                // We'd like to check the behavior in case that real selection
+                // and the cached selection are mismatched.
+                getSelection().removeAllRanges();

[yoichio, 2015/11/17 05:56:40]

Could you have |elt.selectionStart = elt.selectionEnd = 0 | 
 to assure Element::focus sets selectionStart/End ?

[tkent, 2015/11/17 06:02:45]

Setting 0 to them makes unable to check the behavior correctness because we
wrongly returns 0,0 in focus event handler. See crbug.com/526516 .
Adding |selectionStart = selectionEnd = 7| explicitly would make sense.

[tkent, 2015/11/17 06:24:54]

I added it to new patch set.

+                elt.onfocus = function() { display(elt); };
+                elt.focus();
+
                 elt.value = "";
             }
             function testButtonSelectionAccess(button, access)
@@ -121,4 +132,4 @@
         <hr />
         <p id="console"></p>
     </body>
-</html>
+</html>