ClipboardPipeline (clipboard)
@ckeditor/ckeditor5-clipboard/src/clipboardpipeline
The clipboard pipeline feature. It is responsible for intercepting the paste
and drop
events and
passing the pasted content through a series of events in order to insert it into the editor's content.
It also handles the cut
and copy
events to fill the native clipboard with the serialized editor's data.
Input pipeline
The behavior of the default handlers (all at a low
priority):
Event: paste
or drop
- Translates the event data.
- Fires the
view.Document#clipboardInput
event.
Event: view.Document#clipboardInput
- If the
data.content
event field is already set (by some listener on a higher priority), it takes this content and fires the event from the last point. - Otherwise, it retrieves
text/html
ortext/plain
fromdata.dataTransfer
. - Normalizes the raw data by applying simple filters on string data.
- Processes the raw data to
view.DocumentFragment
with theDataController#htmlProcessor
. - Fires the
ClipboardPipeline#inputTransformation
event with the view document fragment in thedata.content
event field.
Event: ClipboardPipeline#inputTransformation
- Converts
view.DocumentFragment
from thedata.content
field tomodel.DocumentFragment
. - Fires the
ClipboardPipeline#contentInsertion
event with the model document fragment in thedata.content
event field. Note: TheClipboardPipeline#contentInsertion
event is fired within a model change block to allow other handlers to run in the same block without post-fixers called in between (i.e., the selection post-fixer).
Event: ClipboardPipeline#contentInsertion
- Calls
model.insertContent()
to insertdata.content
at the current selection position.
Output pipeline
The behavior of the default handlers (all at a low
priority):
Event: copy
, cut
or dragstart
- Retrieves the selected
model.DocumentFragment
by callingmodel#getSelectedContent()
. - Converts the model document fragment to
view.DocumentFragment
. - Fires the
view.Document#clipboardOutput
event with the view document fragment in thedata.content
event field.
Event: view.Document#clipboardOutput
- Processes
data.content
to HTML and plain text with theDataController#htmlProcessor
. - Updates the
data.dataTransfer
data fortext/html
andtext/plain
with the processed data. - For the
cut
method, callsmodel.deleteContent()
on the current selection.
Read more about the clipboard integration in the clipboard deep-dive guide.
Filtering
Properties
-
The editor instance.
Note that most editors implement the
ui
property. However, editors with an external UI (i.e. Bootstrap-based) or a headless editor may not have this property or throw an error when accessing it.Because of above, to make plugins more universal, it is recommended to split features into:
-
inherited observable
isEnabled : boolean
module:clipboard/clipboardpipeline~ClipboardPipeline#isEnabled
Flag indicating whether a plugin is enabled or disabled. A disabled plugin will not transform text.
Plugin can be simply disabled like that:
// Disable the plugin so that no toolbars are visible. editor.plugins.get( 'TextTransformation' ).isEnabled = false;
You can also use
forceDisabled
method.
Static properties
-
readonly inherited static
isContextPlugin : false
module:clipboard/clipboardpipeline~ClipboardPipeline.isContextPlugin
-
readonly static
isOfficialPlugin : true
module:clipboard/clipboardpipeline~ClipboardPipeline.isOfficialPlugin
-
readonly inherited static
isPremiumPlugin : boolean
module:clipboard/clipboardpipeline~ClipboardPipeline.isPremiumPlugin
-
readonly static
pluginName : 'ClipboardPipeline'
module:clipboard/clipboardpipeline~ClipboardPipeline.pluginName
-
readonly static
requires : readonly tuple
module:clipboard/clipboardpipeline~ClipboardPipeline.requires
Methods
-
-
inherited
bind( bindProperty1, bindProperty2 ) → DualBindChain<K1, ClipboardPipeline[ K1 ], K2, ClipboardPipeline[ K2 ]>
module:clipboard/clipboardpipeline~ClipboardPipeline#bind:DUAL_BIND
Binds observable properties to other objects implementing the
Observable
interface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
button
and an associatedcommand
(bothObservable
).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
or even shorter:
button.bind( 'isEnabled' ).to( command );
which works in the following way:
button.isEnabled
instantly equalscommand.isEnabled
,- whenever
command.isEnabled
changes,button.isEnabled
will immediately reflect its value.
Note: To release the binding, use
unbind
.You can also "rename" the property in the binding by specifying the new name in the
to()
chain:button.bind( 'isEnabled' ).to( command, 'isWorking' );
It is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );
which corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );
The binding can include more than one observable, combining multiple data sources in a custom callback:
button.bind( 'isEnabled' ).to( command, 'isEnabled', ui, 'isVisible', ( isCommandEnabled, isUIVisible ) => isCommandEnabled && isUIVisible );
Using a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );
It is also possible to bind to the same property in an array of observables. To bind a
button
to multiple commands (alsoObservables
) so that each and every one of them must be enabled for the button to become enabled, use the following code:button.bind( 'isEnabled' ).toMany( [ commandA, commandB, commandC ], 'isEnabled', ( isAEnabled, isBEnabled, isCEnabled ) => isAEnabled && isBEnabled && isCEnabled );
Type parameters
K1
K2
Parameters
bindProperty1 : K1
Observable property that will be bound to other observable(s).
bindProperty2 : K2
Observable property that will be bound to other observable(s).
Returns
DualBindChain<K1, ClipboardPipeline[ K1 ], K2, ClipboardPipeline[ K2 ]>
The bind chain with the
to()
andtoMany()
methods.
-
inherited
bind( bindProperties ) → MultiBindChain
module:clipboard/clipboardpipeline~ClipboardPipeline#bind:MANY_BIND
Binds observable properties to other objects implementing the
Observable
interface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
button
and an associatedcommand
(bothObservable
).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
or even shorter:
button.bind( 'isEnabled' ).to( command );
which works in the following way:
button.isEnabled
instantly equalscommand.isEnabled
,- whenever
command.isEnabled
changes,button.isEnabled
will immediately reflect its value.
Note: To release the binding, use
unbind
.You can also "rename" the property in the binding by specifying the new name in the
to()
chain:button.bind( 'isEnabled' ).to( command, 'isWorking' );
It is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );
which corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );
The binding can include more than one observable, combining multiple data sources in a custom callback:
button.bind( 'isEnabled' ).to( command, 'isEnabled', ui, 'isVisible', ( isCommandEnabled, isUIVisible ) => isCommandEnabled && isUIVisible );
Using a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );
It is also possible to bind to the same property in an array of observables. To bind a
button
to multiple commands (alsoObservables
) so that each and every one of them must be enabled for the button to become enabled, use the following code:button.bind( 'isEnabled' ).toMany( [ commandA, commandB, commandC ], 'isEnabled', ( isAEnabled, isBEnabled, isCEnabled ) => isAEnabled && isBEnabled && isCEnabled );
Parameters
bindProperties : Array<'off' | 'on' | 'once' | 'listenTo' | 'stopListening' | 'fire' | 'delegate' | 'stopDelegating' | 'set' | 'bind' | 'unbind' | 'decorate' | 'destroy' | 'isEnabled' | 'init' | 'editor' | 'forceDisabled' | 'clearForceDisabled' | '_fireOutputTransformationEvent'>
Observable properties that will be bound to other observable(s).
Returns
MultiBindChain
The bind chain with the
to()
andtoMany()
methods.
-
inherited
bind( bindProperty ) → SingleBindChain<K, ClipboardPipeline[ K ]>
module:clipboard/clipboardpipeline~ClipboardPipeline#bind:SINGLE_BIND
Binds observable properties to other objects implementing the
Observable
interface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
button
and an associatedcommand
(bothObservable
).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
or even shorter:
button.bind( 'isEnabled' ).to( command );
which works in the following way:
button.isEnabled
instantly equalscommand.isEnabled
,- whenever
command.isEnabled
changes,button.isEnabled
will immediately reflect its value.
Note: To release the binding, use
unbind
.You can also "rename" the property in the binding by specifying the new name in the
to()
chain:button.bind( 'isEnabled' ).to( command, 'isWorking' );
It is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );
which corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );
The binding can include more than one observable, combining multiple data sources in a custom callback:
button.bind( 'isEnabled' ).to( command, 'isEnabled', ui, 'isVisible', ( isCommandEnabled, isUIVisible ) => isCommandEnabled && isUIVisible );
Using a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );
It is also possible to bind to the same property in an array of observables. To bind a
button
to multiple commands (alsoObservables
) so that each and every one of them must be enabled for the button to become enabled, use the following code:button.bind( 'isEnabled' ).toMany( [ commandA, commandB, commandC ], 'isEnabled', ( isAEnabled, isBEnabled, isCEnabled ) => isAEnabled && isBEnabled && isCEnabled );
Type parameters
K
Parameters
bindProperty : K
Observable property that will be bound to other observable(s).
Returns
SingleBindChain<K, ClipboardPipeline[ K ]>
The bind chain with the
to()
andtoMany()
methods.
-
inherited
clearForceDisabled( id ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#clearForceDisabled
Clears forced disable previously set through
forceDisabled
. SeeforceDisabled
.Parameters
id : string
Unique identifier, equal to the one passed in
forceDisabled
call.
Returns
void
-
inherited
decorate( methodName ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#decorate
Turns the given methods of this object into event-based ones. This means that the new method will fire an event (named after the method) and the original action will be plugged as a listener to that event.
Read more in the dedicated guide covering the topic of decorating methods with some additional examples.
Decorating the method does not change its behavior (it only adds an event), but it allows to modify it later on by listening to the method's event.
For example, to cancel the method execution the event can be stopped:
class Foo extends ObservableMixin() { constructor() { super(); this.decorate( 'method' ); } method() { console.log( 'called!' ); } } const foo = new Foo(); foo.on( 'method', ( evt ) => { evt.stop(); }, { priority: 'high' } ); foo.method(); // Nothing is logged.
Note: The high priority listener has been used to execute this particular callback before the one which calls the original method (which uses the "normal" priority).
It is also possible to change the returned value:
foo.on( 'method', ( evt ) => { evt.return = 'Foo!'; } ); foo.method(); // -> 'Foo'
Finally, it is possible to access and modify the arguments the method is called with:
method( a, b ) { console.log( `${ a }, ${ b }` ); } // ... foo.on( 'method', ( evt, args ) => { args[ 0 ] = 3; console.log( args[ 1 ] ); // -> 2 }, { priority: 'high' } ); foo.method( 1, 2 ); // -> '3, 2'
Parameters
methodName : 'off' | 'on' | 'once' | 'listenTo' | 'stopListening' | 'fire' | 'delegate' | 'stopDelegating' | 'set' | 'bind' | 'unbind' | 'decorate' | 'destroy' | 'isEnabled' | 'init' | 'editor' | 'forceDisabled' | 'clearForceDisabled' | '_fireOutputTransformationEvent'
Name of the method to decorate.
Returns
void
-
inherited
delegate( events ) → EmitterMixinDelegateChain
module:clipboard/clipboardpipeline~ClipboardPipeline#delegate
Delegates selected events to another
Emitter
. For instance:emitterA.delegate( 'eventX' ).to( emitterB ); emitterA.delegate( 'eventX', 'eventY' ).to( emitterC );
then
eventX
is delegated (fired by)emitterB
andemitterC
along withdata
:emitterA.fire( 'eventX', data );
and
eventY
is delegated (fired by)emitterC
along withdata
:emitterA.fire( 'eventY', data );
Parameters
events : Array<string>
Event names that will be delegated to another emitter.
Returns
-
Destroys the plugin.
Note: This method is optional. A plugin instance does not need to have it defined.
Returns
void
-
inherited
fire( eventOrInfo, args ) → GetEventInfo<TEvent>[ 'return' ]
module:clipboard/clipboardpipeline~ClipboardPipeline#fire
Fires an event, executing all callbacks registered for it.
The first parameter passed to callbacks is an
EventInfo
object, followed by the optionalargs
provided in thefire()
method call.Type parameters
Parameters
eventOrInfo : GetNameOrEventInfo<TEvent>
The name of the event or
EventInfo
object if event is delegated.args : TEvent[ 'args' ]
Additional arguments to be passed to the callbacks.
Returns
GetEventInfo<TEvent>[ 'return' ]
By default the method returns
undefined
. However, the return value can be changed by listeners through modification of theevt.return
's property (the event info is the first param of every callback).
-
inherited
forceDisabled( id ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#forceDisabled
Disables the plugin.
Plugin may be disabled by multiple features or algorithms (at once). When disabling a plugin, unique id should be passed (e.g. feature name). The same identifier should be used when enabling back the plugin. The plugin becomes enabled only after all features enabled it back.
Disabling and enabling a plugin:
plugin.isEnabled; // -> true plugin.forceDisabled( 'MyFeature' ); plugin.isEnabled; // -> false plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> true
Plugin disabled by multiple features:
plugin.forceDisabled( 'MyFeature' ); plugin.forceDisabled( 'OtherFeature' ); plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> false plugin.clearForceDisabled( 'OtherFeature' ); plugin.isEnabled; // -> true
Multiple disabling with the same identifier is redundant:
plugin.forceDisabled( 'MyFeature' ); plugin.forceDisabled( 'MyFeature' ); plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> true
Note: some plugins or algorithms may have more complex logic when it comes to enabling or disabling certain plugins, so the plugin might be still disabled after
clearForceDisabled
was used.Parameters
id : string
Unique identifier for disabling. Use the same id when enabling back the plugin.
Returns
void
-
init() → void
module:clipboard/clipboardpipeline~ClipboardPipeline#init
-
inherited
listenTo( emitter, event, callback, [ options ] ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#listenTo:BASE_EMITTER
Registers a callback function to be executed when an event is fired in a specific (emitter) object.
Events can be grouped in namespaces using
:
. When namespaced event is fired, it additionally fires all callbacks for that namespace.// myEmitter.on( ... ) is a shorthand for myEmitter.listenTo( myEmitter, ... ). myEmitter.on( 'myGroup', genericCallback ); myEmitter.on( 'myGroup:myEvent', specificCallback ); // genericCallback is fired. myEmitter.fire( 'myGroup' ); // both genericCallback and specificCallback are fired. myEmitter.fire( 'myGroup:myEvent' ); // genericCallback is fired even though there are no callbacks for "foo". myEmitter.fire( 'myGroup:foo' );
An event callback can stop the event and set the return value of the
fire
method.Type parameters
Parameters
emitter : Emitter
The object that fires the event.
event : TEvent[ 'name' ]
The name of the event.
callback : GetCallback<TEvent>
The function to be called on event.
[ options ] : GetCallbackOptions<TEvent>
Additional options.
Returns
void
-
Stops executing the callback on the given event. Shorthand for
this.stopListening( this, event, callback )
.Parameters
event : string
The name of the event.
callback : Function
The function to stop being called.
Returns
void
-
inherited
on( event, callback, [ options ] ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#on
Registers a callback function to be executed when an event is fired.
Shorthand for
this.listenTo( this, event, callback, options )
(it makes the emitter listen on itself).Type parameters
Parameters
event : TEvent[ 'name' ]
The name of the event.
callback : GetCallback<TEvent>
The function to be called on event.
[ options ] : GetCallbackOptions<TEvent>
Additional options.
Returns
void
-
inherited
once( event, callback, [ options ] ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#once
Registers a callback function to be executed on the next time the event is fired only. This is similar to calling
on
followed byoff
in the callback.Type parameters
Parameters
event : TEvent[ 'name' ]
The name of the event.
callback : GetCallback<TEvent>
The function to be called on event.
[ options ] : GetCallbackOptions<TEvent>
Additional options.
Returns
void
-
Creates and sets the value of an observable properties of this object. Such a property becomes a part of the state and is observable.
It accepts a single object literal containing key/value pairs with properties to be set.
This method throws the
observable-set-cannot-override
error if the observable instance already has a property with the given property name. This prevents from mistakenly overriding existing properties and methods, but means thatfoo.set( 'bar', 1 )
may be slightly slower thanfoo.bar = 1
.In TypeScript, those properties should be declared in class using
declare
keyword. In example:public declare myProp1: number; public declare myProp2: string; constructor() { this.set( { 'myProp1: 2, 'myProp2: 'foo' } ); }
Parameters
values : object
An object with
name=>value
pairs.
Returns
void
-
inherited
set( name, value ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#set:KEY_VALUE
Creates and sets the value of an observable property of this object. Such a property becomes a part of the state and is observable.
This method throws the
observable-set-cannot-override
error if the observable instance already has a property with the given property name. This prevents from mistakenly overriding existing properties and methods, but means thatfoo.set( 'bar', 1 )
may be slightly slower thanfoo.bar = 1
.In TypeScript, those properties should be declared in class using
declare
keyword. In example:public declare myProp: number; constructor() { this.set( 'myProp', 2 ); }
Type parameters
K
Parameters
name : K
The property's name.
value : ClipboardPipeline[ K ]
The property's value.
Returns
void
-
inherited
stopDelegating( [ event ], [ emitter ] ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#stopDelegating
Stops delegating events. It can be used at different levels:
- To stop delegating all events.
- To stop delegating a specific event to all emitters.
- To stop delegating a specific event to a specific emitter.
Parameters
[ event ] : string
The name of the event to stop delegating. If omitted, stops it all delegations.
[ emitter ] : Emitter
(requires
event
) The object to stop delegating a particular event to. If omitted, stops delegation ofevent
to all emitters.
Returns
void
-
inherited
stopListening( [ emitter ], [ event ], [ callback ] ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#stopListening:BASE_STOP
Stops listening for events. It can be used at different levels:
- To stop listening to a specific callback.
- To stop listening to a specific event.
- To stop listening to all events fired by a specific object.
- To stop listening to all events fired by all objects.
Parameters
[ emitter ] : Emitter
The object to stop listening to. If omitted, stops it for all objects.
[ event ] : string
(Requires the
emitter
) The name of the event to stop listening to. If omitted, stops it for all events fromemitter
.[ callback ] : Function
(Requires the
event
) The function to be removed from the call list for the givenevent
.
Returns
void
-
inherited
unbind( unbindProperties ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#unbind
Removes the binding created with
bind
.// Removes the binding for the 'a' property. A.unbind( 'a' ); // Removes bindings for all properties. A.unbind();
Parameters
unbindProperties : Array<'off' | 'on' | 'once' | 'listenTo' | 'stopListening' | 'fire' | 'delegate' | 'stopDelegating' | 'set' | 'bind' | 'unbind' | 'decorate' | 'destroy' | 'isEnabled' | 'init' | 'editor' | 'forceDisabled' | 'clearForceDisabled' | '_fireOutputTransformationEvent'>
Observable properties to be unbound. All the bindings will be released if no properties are provided.
Returns
void
-
internal
_fireOutputTransformationEvent( dataTransfer, selection, method ) → void
module:clipboard/clipboardpipeline~ClipboardPipeline#_fireOutputTransformationEvent
Fires Clipboard
'outputTransformation'
event for given parameters.Parameters
dataTransfer : DataTransfer
selection : Selection | DocumentSelection
method : 'copy' | 'cut' | 'dragstart'
Returns
void
-
-
private
_setupPasteDrop() → void
module:clipboard/clipboardpipeline~ClipboardPipeline#_setupPasteDrop
Events
-
inherited
change:isEnabled( eventInfo, name, value, oldValue )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:change:isEnabled
Fired when the
isEnabled
property changed value.Parameters
eventInfo : EventInfo
An object containing information about the fired event.
name : string
Name of the changed property (
isEnabled
).value : boolean
New value of the
isEnabled
property with given key ornull
, if operation should remove property.oldValue : boolean
Old value of the
isEnabled
property with given key ornull
, if property was not set before.
-
inherited
change:{property}( eventInfo, name, value, oldValue )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:change:{property}
Fired when a property changed value.
observable.set( 'prop', 1 ); observable.on<ObservableChangeEvent<number>>( 'change:prop', ( evt, propertyName, newValue, oldValue ) => { console.log( `${ propertyName } has changed from ${ oldValue } to ${ newValue }` ); } ); observable.prop = 2; // -> 'prop has changed from 1 to 2'
Parameters
eventInfo : EventInfo
An object containing information about the fired event.
name : string
The property name.
value : TValue
The new property value.
oldValue : TValue
The previous property value.
-
contentInsertion( eventInfo, data )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:contentInsertion
Fired with the
content
,dataTransfer
,method
, andtargetRanges
properties:- The
content
which comes from the clipboard (was pasted or dropped) should be processed in order to be inserted into the editor. - The
dataTransfer
object is available in case the transformation functions need access to the raw clipboard data. - The
method
indicates the original DOM event (for example'drop'
or'paste'
). - The
targetRanges
property is an array of view ranges (it is available only for'drop'
).
Event handlers can modify the content according to the final insertion position.
It is a part of the clipboard input pipeline.
Note: You should not stop this event if you want to change the input data. You should modify the
content
property instead.Parameters
eventInfo : EventInfo
An object containing information about the fired event.
data : ClipboardContentInsertionData
The event data.
Related:
- The
-
inputTransformation( eventInfo, data )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:inputTransformation
Fired with the
content
,dataTransfer
,method
, andtargetRanges
properties:- The
content
which comes from the clipboard (it was pasted or dropped) should be processed in order to be inserted into the editor. - The
dataTransfer
object is available in case the transformation functions need access to the raw clipboard data. - The
method
indicates the original DOM event (for example'drop'
or'paste'
). - The
targetRanges
property is an array of view ranges (it is available only for'drop'
).
It is a part of the clipboard input pipeline.
Note: You should not stop this event if you want to change the input data. You should modify the
content
property instead.Parameters
eventInfo : EventInfo
An object containing information about the fired event.
data : ClipboardInputTransformationData
The event data.
Related:
- The
-
outputTransformation( eventInfo, data )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:outputTransformation
Fired on event-copy, event-cut and event-dragstart. The content can be processed before it ends up in the clipboard.
It is a part of the clipboard output pipeline.
Parameters
eventInfo : EventInfo
An object containing information about the fired event.
data : ClipboardOutputTransformationData
The event data.
-
inherited
set:isEnabled( eventInfo, name, value, oldValue )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:set:isEnabled
Fired when the
isEnabled
property is going to be set but is not set yet (before thechange
event is fired).Parameters
eventInfo : EventInfo
An object containing information about the fired event.
name : string
Name of the changed property (
isEnabled
).value : boolean
New value of the
isEnabled
property with given key ornull
, if operation should remove property.oldValue : boolean
Old value of the
isEnabled
property with given key ornull
, if property was not set before.
-
inherited
set:{property}( eventInfo, name, value, oldValue )
module:clipboard/clipboardpipeline~ClipboardPipeline#event:set:{property}
Fired when a property value is going to be set but is not set yet (before the
change
event is fired).You can control the final value of the property by using the event's
return
property.observable.set( 'prop', 1 ); observable.on<ObservableSetEvent<number>>( 'set:prop', ( evt, propertyName, newValue, oldValue ) => { console.log( `Value is going to be changed from ${ oldValue } to ${ newValue }` ); console.log( `Current property value is ${ observable[ propertyName ] }` ); // Let's override the value. evt.return = 3; } ); observable.on<ObservableChangeEvent<number>>( 'change:prop', ( evt, propertyName, newValue, oldValue ) => { console.log( `Value has changed from ${ oldValue } to ${ newValue }` ); } ); observable.prop = 2; // -> 'Value is going to be changed from 1 to 2' // -> 'Current property value is 1' // -> 'Value has changed from 1 to 3'
Note: The event is fired even when the new value is the same as the old value.
Parameters
eventInfo : EventInfo
An object containing information about the fired event.
name : string
The property name.
value : TValue
The new property value.
oldValue : TValue
The previous property value.
Every day, we work hard to keep our documentation complete. Have you spotted outdated information? Is something missing? Please report it via our issue tracker.
With the release of version 42.0.0, we have rewritten much of our documentation to reflect the new import paths and features. We appreciate your feedback to help us ensure its accuracy and completeness.