New changes:
2464397 Move toolbar floating code up to the target
11bdc21 Separate SA target into Mobile and Desktop
7ab3389 AlignableContextItem: Fix styling in mobile
758619f CONTRIBUTING.md: Update file paths and build instructions
Local changes to mw.Target to handle toolbar floating.
Change-Id: I0751817e3a6668b120134bfcb6c611b121a46501
New changes:
a56746e Ensure demo init script runs last
ab6a1bd Context emits resize events
564701a Provide a context item for table cells in mobile
9f92a0f MobileWindowManager: Bring in styles from MW-Minerva
Change-Id: If0da9079bbab6f930979ed17be3b27cb0a5bea60
Also use named classes for hiding toolbars, and move the
MobileFrontend overlay z-index hack out to that repo.
Depends on Ia46e6b4d7a in MobileFrontend.
Change-Id: I0e1f527446fd10fde5dd3107e6467fd2c8f621b2
New changes:
552fec6 MobileContext: Use frameless buttons, fix vertical heights/alignments
ebb4d08 Emit blur/focus events from the surface model
Change-Id: I9227a8795378826f1cee6dc2d3ac562b9970b9e2
Split the toolbar into two modes depending on if the surface is focused:
* When unfocused, show a hamburger containing back and source switch
* When focused, show editing tools, and a check button to unfocus
For the editing toolbar, space the tools out using table-cell layout
and hide labels below 480px.
Depends on I06813e3ff in core (surface blur method).
Bug: T93325
Change-Id: Ibf09cb29019d7a71e1e144b326710b1f6506cd0c
New changes:
3753f8b ve.ui.ToolbarDialog.css: Move Apex-specific hacks to Apex stylesheet
4650555 Localisation updates from https://translatewiki.net.
40f31a2 DebugBar: Re-style linmod dump hide button to left with '^' icon
5ff7c26 ve.ui.Surface: Teardown the view after window managers
03193a6 ve.ce.Surface: Provide #blur to pair with #focus
ab26ac6 Fixup I06813e3ff: Activate surface before blurring
4f2e832 Flag back/cancel actions so they can be restyled in mobile
a499a73 Localisation updates from https://translatewiki.net.
Change-Id: Iefdd8e7db47e6a53913c0a95a95559fe2c0a9dc2
* On save, VE will now fetch and append modules and jsconfigvars to the save
event, which respectively contains necessary JS config module data and the
list of required modules to be added on the page.
* The jsconfigvars are now properly added to mw.config on edit save.
* If any new modules are now required by the page after an edit, they will be
loaded by ResourceLoader through mw.loader.load.
Change-Id: Ib3990078a22ad9e46debf3ce174e7cf27b86d944
When you bind to your own events you're probably using the wrong
design pattern.
The events are kept (without arguments) for the purpose of tracking.
Change-Id: I6983319f9e0ca179e609afb00c821e3eab2161c9
New changes:
87c538a PasteRules#plainText: Fallback if rules.external is undefined
7155191 Localisation updates from https://translatewiki.net.
c2d03ea ToolContextItem: Use the target's command registry
d196838 DataTransferHandler: Improve aborting and resolution/rejection
009190e Allow the target to specify a DataTransferHandler factory
0ea9439 Split out basic functionality of tableCell so other nodes can behave as cells
999a5da ve.ce.TableCellableNode: Only apply title to nodes which are cellable
Change-Id: I56a73a26f21a6e22b6bafc850cdee35397e5d15d
Allows us to rename onSaveEvent back to onSave.
Before this change,
* ve.init.mw.Target.prototype.save ->
* ve.init.mw.Target.prototype.onSave, emit save event ->
* ve.init.mw.DesktopArticleTarget.prototype.onSaveEvent (or MF equivalent)
With this change,
* ve.init.mw.Target.prototype.save ->
* ve.init.mw.Target.prototype.saveSuccess, emit save event ->
* ve.init.mw.DesktopArticleTarget.prototype.onSave (or MF equivalent)
Change-Id: I016262b38a941c93c0978391491baa6d5a32fe28
Don't try to apply page settings changes to meta list unless we're actually
applying. "Cancel" shouldn't apply changes, we have another button for that.
Bug: T97682
Change-Id: I9eae20c3946b315413340268e44537cdbec2e455
