mirror of
https://github.com/WordPress/WordPress.git
synced 2024-08-31 01:59:47 +02:00
a5478d7adb
* The way that the JS modules for media are currently set up turns the existing global `wp.media` namespace into a read-only API, this is bad. * For the existing module implementation to work with plugins, those looking to override or extend a class would have to modify their own plugin to use `browserify` - we can't expect this to happen * Because the general way that plugins override media classes is via machete (resetting them to something else), we cannot use `require( 'module' )` in the internal code for media modules We CAN continue to use `require( 'fun/js' )` in the manifests for media. Future code/projects should carefully consider what is made to be public API. In 3.5, EVERYTHING was made public, so everything shall remain public. See #31684, #28510. Built from https://develop.svn.wordpress.org/trunk@31935 git-svn-id: http://core.svn.wordpress.org/trunk@31914 1a063a9b-81f0-0310-95a4-ce76da25c4cd
29 lines
614 B
JavaScript
29 lines
614 B
JavaScript
/*globals wp */
|
|
|
|
/**
|
|
* wp.media.controller.EditAttachmentMetadata
|
|
*
|
|
* A state for editing an attachment's metadata.
|
|
*
|
|
* @class
|
|
* @augments wp.media.controller.State
|
|
* @augments Backbone.Model
|
|
*/
|
|
var l10n = wp.media.view.l10n,
|
|
EditAttachmentMetadata;
|
|
|
|
EditAttachmentMetadata = wp.media.controller.State.extend({
|
|
defaults: {
|
|
id: 'edit-attachment',
|
|
// Title string passed to the frame's title region view.
|
|
title: l10n.attachmentDetails,
|
|
// Region mode defaults.
|
|
content: 'edit-metadata',
|
|
menu: false,
|
|
toolbar: false,
|
|
router: false
|
|
}
|
|
});
|
|
|
|
module.exports = EditAttachmentMetadata;
|