New changes:
7e271a4 Add containsRange method to ve.Range
4745931 Convert all instances of assert.equal to assert.strictEqual
a8fab7a Rename frequency to pollInterval in SurfaceObserver
8e8217e Bind ve.ce.Surface#onDocumentMouseUp to the entire document on mousedown
29029c3 Localisation updates from https://translatewiki.net.
8345488 DomRange / getOffset edge cases
3c4826a Cache $documentNode in surface view
2fcc4c0 Trigger selection update on selectionchange or mousemove events
67aa7dd Fix JS error due to typo in dm.Converter
Change-Id: I846318357ba1f3a8ee59c4384b5dceef7a9e70ff
New changes:
3e2537f Split getSelectionRect into bounding and inline
b73d010 Kill rangy (almost)
38207f4 Kill rangy: Vol. 2
b392d88 Rangy's dead honey, rangy's dead
Local changes:
* Remove references to rangy
Change-Id: I900eb3e36a564a526c01a5e00f8ea31a1ac9c0a3
Category redirect stuff is currently broken because of I5c536697, but no one seems to have noticed.
Fix bug 69886 while we're here
Bug: 69886
Change-Id: I62cf23d0e86bc43d739bb4c4610a5a852146fa3f
New changes:
3f5029c Add a secondary label (Edit) to ContextItemWidget
807d377 Update OOjs UI to v0.1.0-pre (cc3c62607c)
45d82b6 Localisation updates from https://translatewiki.net.
Change-Id: Ie3104507d188ac8d3c45698bfd345c3c1146a938
Rather than modifying $wgResourceModules at run-time, use
a subclass of ResourceLoaderFileModule to add the messages
in the constructor.
Change-Id: I9cf99891ed186afb6aa63501edced692117a7c50
Inserting a new external link from the link inspector when nothing is
selected (collapsed selection) will now produce an autonumbered external
link ('link/mwNumberedExternal' node, corresponding to wikitext
"[http://example.com]"). It used to produce annotated link text
('link/mwExternal' annotation, corresponding to wikitext
"[http://example.comhttp://example.com]" or "http://example.com").
Depends on two commits in VisualEditor/VisualEditor:
* Icc2e368a to insert unannotated content from the inspector.
* I40cd4d5a to insert non-text content from the inspector.
Bug: 51309
Change-Id: Ie4a633ed42907551337a62d96d0abd59e208d49d
Before sending new searches to the API, abort the previous ones if
they were not resolved. This will assure that the result presented
on the screen is valid to the latest search that was done even if
the user types quickly and sends many async requests simultaneously.
Bug: 67438
Change-Id: If88123019bfa972520e9db7c627a7f4cd8fc2526
setChanged() was renamed to checkChanged(), but one call wasn't
updated. This was causing JS errors in a documentUpdate event
handler, which caused pawn nastiness.
Bug: 70450
Change-Id: I71e576638f9e2fde450f4412229cf980e6ba7e10
After resolving the search queries to the API, make sure to display
or hide (!) the "no results" message.
Bug: 67438
Change-Id: I518fbf5ae18bb2265710600516d556c60e2b4924
