Last modified: 2014-03-11 02:05:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T51438, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49438 - VisualEditor: Tools should be able to specify contexts they can/can't operate in themselves
VisualEditor: Tools should be able to specify contexts they can/can't operate...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Technical Debt (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-11 15:31 UTC by Roan Kattouw
Modified: 2014-03-11 02:05 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Roan Kattouw 2013-06-11 15:31:49 UTC
Right now we use things like:

toolbarSubset = ve.init.mw.ViewPageTarget.static.getToolbarSubset( [
	// Can't have nested references
	'mwReference',
	// Lists not properly supported by PHP parser
	'number', 'bullet', 'outdent', 'indent'
] );

in ve.ui.MWReferenceDialog and ve.ui.MWMediaDialog

Instead, whether a given tool makes sense in a reference or image context (or in a subeditor in general) should be defined in the tool itself.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links