The down arrow is no longer default, so it needs to be specified
explicitly.
Updates submodule to include indicator changes
(see I0a1faef11a1e7e6ea3e44275c85f2efafae4dc9a)
Change-Id: I32aef3ea2e66fd823aeb07dac06cfefba9954270
New changes:
d89cc15 Add sticky static property to inspector tools
5d8e3fd Fix more copyright headers not updated to 2014
e97f100 Always use absolute URLs in external links in the clipboard
9cc0a8d Fix descriptions of ve.dm.Surface#change tests
16fda03 Check for valid offset when calculating insertion annotations
a156f76 Add 'get range on change' toggle button to standalone demo
eca979d Move initial selection to first content offset
Change-Id: Ibdc130775613af50014d9effe0f2e39bba501e87
New changes:
1f7e944 Add method to fully destroy a target
6cda4b7 Fix scrolling back and forth on copy/paste in Firefox
34d2c79 demos: Support back/forward navigation
787deba Replace dump model loop with event triggered dump
94b1b40 Do not use global document
5cd4227 Always use current surface on demo page
f74f6d8 Make DefinitionListItemNodes splittable
Change-Id: If0a7beed97c4fa6759fbbb989d7ef979c0a1e4e2
* Add lib/ve.
* Remove modules provided by VisualEditor core.
* Update paths.
* Remove VisualEditor core specific things from Gruntfile.
* Remove entries from external.js already in lib/ve/.docs/external.js.
* Implement build script to compose a jsduck index that includes
all of VisualEditor core. Right now it includes VisualEditor's
index as-is, and because those patterns (e.g. ve.dm.*Node) will
also MW subclasses this means our category page will include
MW classes under "VisualEditor (core)" (before the repo split,
this was intentional).
This is inevitable unless we list every class individually, or
(the plan) until we move the MW subclasses out of the ve.*
namespace and into mw.* somewhere.
Bug: 45342
Change-Id: Iff45cd555430634c9fc341fd3b177c1e0625300b
