Boris Zbarsky 77e7a5575a Bug 1343037 part 6. Simplify the setup around the editor state's GetSelectionRange function. r=ehsan ... Really, there are only two cases we need to worry about. Either IsSelectionCached(), and then our SelectionProperties has the data we want, or not and then we have a non-null mSelCon which has the data we want. Since we are now using cached selection state a lot more (instead of initializing the editor whenever someone asks for selection state), we need to actually update it more correctly when .value is set. And since we now update the cached selection state for the case when .value has been set (to point to the end of the text), we need to change HTMLInputElement::HasCachedSelection to return false for that case. Otherwise we will always do eager editor init on value set. We handle that by not doing eager init if the cached selection is collapsed. The web platform test changes test the "update on .value set" behavior. They fail without this patch, pass with it. MozReview-Commit-ID: DDU8U4MGb23		2017-03-09 14:44:04 -05:00
..
browser	Bug 1345253 - Use element.firstChild.remove() instead of element.removeChild(element.firstChild), r=jaws.	2017-03-08 10:17:52 +01:00
crashtests	Backed out changeset 27f8d8e9c4dc (bug 1149966) for frequent timeouts in test_form_submission.html	2017-01-09 18:42:17 -08:00
mochitest	Bug 1343037 part 6. Simplify the setup around the editor state's GetSelectionRange function. r=ehsan	2017-03-09 14:44:04 -05:00