DataFilter
Allows to validate elements and element attributes registered by DataSchema.
To enable registered element in the editor, use allowElement method:
dataFilter.allowElement( 'section' );
You can also allow or disallow specific element attributes:
// Allow `data-foo` attribute on `section` element.
dataFilter.allowAttributes( {
name: 'section',
attributes: {
'data-foo': true
}
} );
// Disallow `color` style attribute on 'section' element.
dataFilter.disallowAttributes( {
name: 'section',
styles: {
color: /[\s\S]+/
}
} );
To apply the information about allowed and disallowed attributes in custom integration plugin,
use the processViewAttributes() method.
Properties
-
module:html-support/datafilter~DataFilter#editorThe editor instance.
Note that most editors implement the
uiproperty. 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:
-
isEnabled : booleanmodule:html-support/datafilter~DataFilter#isEnabledFlag 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;Copy codeYou can also use
forceDisabledmethod. -
_allowedAttributes : Matcherprivatereadonlymodule:html-support/datafilter~DataFilter#_allowedAttributesMatcher instance describing rules upon which content attributes should be allowed.
-
_allowedElements : Set<object>privatereadonlymodule:html-support/datafilter~DataFilter#_allowedElementsAllowed element definitions by
allowElementmethod. -
_coupledAttributes : null | Map<string, Array<string>>privatemodule:html-support/datafilter~DataFilter#_coupledAttributesCached map of coupled attributes. Keys are the feature attributes names and values are arrays with coupled GHS attributes names.
-
_dataInitialized : booleanprivatemodule:html-support/datafilter~DataFilter#_dataInitializedIndicates if editor's data controller data has been already initialized.
-
_dataSchema : DataSchemaprivatereadonlymodule:html-support/datafilter~DataFilter#_dataSchemaAn instance of the
DataSchema. -
_disallowedAttributes : Matcherprivatereadonlymodule:html-support/datafilter~DataFilter#_disallowedAttributesMatcher instance describing rules upon which content attributes should be disallowed.
-
_disallowedElements : Set<string>privatereadonlymodule:html-support/datafilter~DataFilter#_disallowedElementsDisallowed element names by
disallowElementmethod.
Static properties
-
isContextPlugin : falsereadonlyinheritedstaticmodule:html-support/datafilter~DataFilter.isContextPlugin -
pluginName : 'DataFilter'readonlystaticmodule:html-support/datafilter~DataFilter.pluginName -
requires : readonly tuplereadonlystaticmodule:html-support/datafilter~DataFilter.requires -
isOfficialPlugin : trueinternalreadonlystaticmodule:html-support/datafilter~DataFilter.isOfficialPlugin -
isPremiumPlugin : booleaninternalreadonlyinheritedstaticmodule:html-support/datafilter~DataFilter.isPremiumPlugin
Methods
-
constructor( editor )module:html-support/datafilter~DataFilter#constructor -
allowAttributes( config ) → voidmodule:html-support/datafilter~DataFilter#allowAttributesAllow the given attributes for view element allowed by
allowElementmethod.Parameters
config : MatcherPatternPattern matching all attributes which should be allowed.
Returns
void
-
allowElement( viewName ) → voidmodule:html-support/datafilter~DataFilter#allowElementAllow the given element in the editor context.
This method will only allow elements described by the
DataSchemaused to create data filter.Note: Rules will be applied just before next data pipeline data init or set.
Parameters
viewName : string | RegExpString or regular expression matching view name.
Returns
void
-
allowEmptyElement( viewName ) → voidmodule:html-support/datafilter~DataFilter#allowEmptyElementAllow the given empty element in the editor context.
This method will only allow elements described by the
DataSchemaused to create data filter.Note: It modifies DataSchema so must be called before registering filtering rules.
Parameters
viewName : stringString or regular expression matching view name.
Returns
void
-
bind( bindProperties ) → ObservableMultiBindChaininheritedmodule:html-support/datafilter~DataFilter#bind:MANY_BINDBinds observable properties to other objects implementing the
Observableinterface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
buttonand an associatedcommand(bothObservable).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );Copy codeor even shorter:
button.bind( 'isEnabled' ).to( command );Copy codewhich works in the following way:
button.isEnabledinstantly equalscommand.isEnabled,- whenever
command.isEnabledchanges,button.isEnabledwill 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' );Copy codeIt is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );Copy codewhich corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );Copy codeThe 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 );Copy codeUsing a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );Copy codeIt is also possible to bind to the same property in an array of observables. To bind a
buttonto 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 );Copy codeParameters
bindProperties : Array<'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'destroy' | 'allowAttributes' | 'disallowAttributes' | 'isEnabled' | 'editor' | 'forceDisabled' | 'clearForceDisabled' | 'loadAllowedConfig' | 'loadDisallowedConfig' | 'loadAllowedEmptyElementsConfig' | 'allowElement' | 'disallowElement' | 'allowEmptyElement' | 'processViewAttributes'>Observable properties that will be bound to other observable(s).
Returns
ObservableMultiBindChainThe bind chain with the
to()andtoMany()methods.
-
bind( bindProperty1, bindProperty2 ) → ObservableDualBindChain<K1, DataFilter[ K1 ], K2, DataFilter[ K2 ]>inheritedmodule:html-support/datafilter~DataFilter#bind:DUAL_BINDBinds observable properties to other objects implementing the
Observableinterface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
buttonand an associatedcommand(bothObservable).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );Copy codeor even shorter:
button.bind( 'isEnabled' ).to( command );Copy codewhich works in the following way:
button.isEnabledinstantly equalscommand.isEnabled,- whenever
command.isEnabledchanges,button.isEnabledwill 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' );Copy codeIt is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );Copy codewhich corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );Copy codeThe 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 );Copy codeUsing a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );Copy codeIt is also possible to bind to the same property in an array of observables. To bind a
buttonto 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 );Copy codeType parameters
K1K2
Parameters
bindProperty1 : K1Observable property that will be bound to other observable(s).
bindProperty2 : K2Observable property that will be bound to other observable(s).
Returns
ObservableDualBindChain<K1, DataFilter[ K1 ], K2, DataFilter[ K2 ]>The bind chain with the
to()andtoMany()methods.
-
bind( bindProperty ) → ObservableSingleBindChain<K, DataFilter[ K ]>inheritedmodule:html-support/datafilter~DataFilter#bind:SINGLE_BINDBinds observable properties to other objects implementing the
Observableinterface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
buttonand an associatedcommand(bothObservable).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );Copy codeor even shorter:
button.bind( 'isEnabled' ).to( command );Copy codewhich works in the following way:
button.isEnabledinstantly equalscommand.isEnabled,- whenever
command.isEnabledchanges,button.isEnabledwill 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' );Copy codeIt is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );Copy codewhich corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );Copy codeThe 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 );Copy codeUsing a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );Copy codeIt is also possible to bind to the same property in an array of observables. To bind a
buttonto 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 );Copy codeType parameters
K
Parameters
bindProperty : KObservable property that will be bound to other observable(s).
Returns
ObservableSingleBindChain<K, DataFilter[ K ]>The bind chain with the
to()andtoMany()methods.
-
clearForceDisabled( id ) → voidinheritedmodule:html-support/datafilter~DataFilter#clearForceDisabledClears forced disable previously set through
forceDisabled. SeeforceDisabled.Parameters
id : stringUnique identifier, equal to the one passed in
forceDisabledcall.
Returns
void
-
decorate( methodName ) → voidinheritedmodule:html-support/datafilter~DataFilter#decorateTurns 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.Copy codeNote: 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'Copy codeFinally, 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'Copy codeParameters
methodName : 'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'destroy' | 'allowAttributes' | 'disallowAttributes' | 'isEnabled' | 'editor' | 'forceDisabled' | 'clearForceDisabled' | 'loadAllowedConfig' | 'loadDisallowedConfig' | 'loadAllowedEmptyElementsConfig' | 'allowElement' | 'disallowElement' | 'allowEmptyElement' | 'processViewAttributes'Name of the method to decorate.
Returns
void
-
delegate( events ) → EmitterMixinDelegateChaininheritedmodule:html-support/datafilter~DataFilter#delegateDelegates selected events to another
Emitter. For instance:emitterA.delegate( 'eventX' ).to( emitterB ); emitterA.delegate( 'eventX', 'eventY' ).to( emitterC );Copy codethen
eventXis delegated (fired by)emitterBandemitterCalong withdata:emitterA.fire( 'eventX', data );Copy codeand
eventYis delegated (fired by)emitterCalong withdata:emitterA.fire( 'eventY', data );Copy codeParameters
events : Array<string>Event names that will be delegated to another emitter.
Returns
-
destroy() → voidinheritedmodule:html-support/datafilter~DataFilter#destroyDestroys the plugin.
Note: This method is optional. A plugin instance does not need to have it defined.
Returns
void
-
disallowAttributes( config ) → voidmodule:html-support/datafilter~DataFilter#disallowAttributesDisallow the given attributes for view element allowed by
allowElementmethod.Parameters
config : MatcherPatternPattern matching all attributes which should be disallowed.
Returns
void
-
disallowElement( viewName ) → voidmodule:html-support/datafilter~DataFilter#disallowElementDisallow the given element in the editor context.
This method will only disallow elements described by the
DataSchemaused to create data filter.Parameters
viewName : string | RegExpString or regular expression matching view name.
Returns
void
-
fire( eventOrInfo, args ) → GetEventInfo<TEvent>[ 'return' ]inheritedmodule:html-support/datafilter~DataFilter#fireFires an event, executing all callbacks registered for it.
The first parameter passed to callbacks is an
EventInfoobject, followed by the optionalargsprovided in thefire()method call.Type parameters
Parameters
eventOrInfo : GetNameOrEventInfo<TEvent>The name of the event or
EventInfoobject 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).
-
forceDisabled( id ) → voidinheritedmodule:html-support/datafilter~DataFilter#forceDisabledDisables 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; // -> trueCopy codePlugin disabled by multiple features:
plugin.forceDisabled( 'MyFeature' ); plugin.forceDisabled( 'OtherFeature' ); plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> false plugin.clearForceDisabled( 'OtherFeature' ); plugin.isEnabled; // -> trueCopy codeMultiple disabling with the same identifier is redundant:
plugin.forceDisabled( 'MyFeature' ); plugin.forceDisabled( 'MyFeature' ); plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> trueCopy codeNote: 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
clearForceDisabledwas used.Parameters
id : stringUnique identifier for disabling. Use the same id when enabling back the plugin.
Returns
void
-
listenTo( emitter, event, callback, [ options ] ) → voidinheritedmodule:html-support/datafilter~DataFilter#listenTo:BASE_EMITTERRegisters 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' );Copy codeAn event callback can stop the event and set the return value of the
firemethod.Type parameters
Parameters
emitter : EmitterThe 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
-
loadAllowedConfig( config ) → voidmodule:html-support/datafilter~DataFilter#loadAllowedConfigLoad a configuration of one or many elements, where their attributes should be allowed.
Note: Rules will be applied just before next data pipeline data init or set.
Parameters
config : Array<MatcherObjectPattern>Configuration of elements that should have their attributes accepted in the editor.
Returns
void
-
loadAllowedEmptyElementsConfig( config ) → voidmodule:html-support/datafilter~DataFilter#loadAllowedEmptyElementsConfigLoad a configuration of one or many elements, where when empty should be allowed.
Note: It modifies DataSchema so must be loaded before registering filtering rules.
Parameters
config : Array<string>Configuration of elements that should be preserved even if empty.
Returns
void
-
loadDisallowedConfig( config ) → voidmodule:html-support/datafilter~DataFilter#loadDisallowedConfigLoad a configuration of one or many elements, where their attributes should be disallowed.
Note: Rules will be applied just before next data pipeline data init or set.
Parameters
config : Array<MatcherObjectPattern>Configuration of elements that should have their attributes rejected from the editor.
Returns
void
-
off( event, callback ) → voidinheritedmodule:html-support/datafilter~DataFilter#offStops executing the callback on the given event. Shorthand for
this.stopListening( this, event, callback ).Parameters
event : stringThe name of the event.
callback : FunctionThe function to stop being called.
Returns
void
-
on( event, callback, [ options ] ) → voidinheritedmodule:html-support/datafilter~DataFilter#onRegisters 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
-
once( event, callback, [ options ] ) → voidinheritedmodule:html-support/datafilter~DataFilter#onceRegisters a callback function to be executed on the next time the event is fired only. This is similar to calling
onfollowed byoffin 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
-
processViewAttributes( viewElement, conversionApi ) → null | GHSViewAttributesmodule:html-support/datafilter~DataFilter#processViewAttributesProcesses all allowed and disallowed attributes on the view element by consuming them and returning the allowed ones.
This method applies the configuration set up by
allowAttributes()anddisallowAttributes()over the given view element by consuming relevant attributes. It returns the allowed attributes that were found on the given view element for further processing by integration code.dispatcher.on( 'element:myElement', ( evt, data, conversionApi ) => { // Get rid of disallowed and extract all allowed attributes from a viewElement. const viewAttributes = dataFilter.processViewAttributes( data.viewItem, conversionApi ); // Do something with them, i.e. store inside a model as a dictionary. if ( viewAttributes ) { conversionApi.writer.setAttribute( 'htmlAttributesOfMyElement', viewAttributes, data.modelRange ); } } );Copy codeParameters
viewElement : ViewElementconversionApi : UpcastConversionApi
Returns
null | GHSViewAttributesObject with following properties:
- attributes Set with matched attribute names.
- styles Set with matched style names.
- classes Set with matched class names.
Related:
-
set( values ) → voidinheritedmodule:html-support/datafilter~DataFilter#set:OBJECTCreates 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-overrideerror 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
declarekeyword. In example:public declare myProp1: number; public declare myProp2: string; constructor() { this.set( { 'myProp1: 2, 'myProp2: 'foo' } ); }Copy codeParameters
values : objectAn object with
name=>valuepairs.
Returns
void
-
set( name, value ) → voidinheritedmodule:html-support/datafilter~DataFilter#set:KEY_VALUECreates 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-overrideerror 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
declarekeyword. In example:public declare myProp: number; constructor() { this.set( 'myProp', 2 ); }Copy codeType parameters
K
Parameters
name : KThe property's name.
value : DataFilter[ K ]The property's value.
Returns
void
-
stopDelegating( [ event ], [ emitter ] ) → voidinheritedmodule:html-support/datafilter~DataFilter#stopDelegatingStops 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 ] : stringThe 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 ofeventto all emitters.
Returns
void
-
stopListening( [ emitter ], [ event ], [ callback ] ) → voidinheritedmodule:html-support/datafilter~DataFilter#stopListening:BASE_STOPStops 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 ] : EmitterThe 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
-
unbind( unbindProperties ) → voidinheritedmodule:html-support/datafilter~DataFilter#unbindRemoves the binding created with
bind.// Removes the binding for the 'a' property. A.unbind( 'a' ); // Removes bindings for all properties. A.unbind();Copy codeParameters
unbindProperties : Array<'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'destroy' | 'allowAttributes' | 'disallowAttributes' | 'isEnabled' | 'editor' | 'forceDisabled' | 'clearForceDisabled' | 'loadAllowedConfig' | 'loadDisallowedConfig' | 'loadAllowedEmptyElementsConfig' | 'allowElement' | 'disallowElement' | 'allowEmptyElement' | 'processViewAttributes'>Observable properties to be unbound. All the bindings will be released if no properties are provided.
Returns
void
-
_addAllowedElement( definition ) → voidprivatemodule:html-support/datafilter~DataFilter#_addAllowedElementAdds allowed element definition and fires registration event.
Parameters
definition : HtmlSupportDataSchemaDefinition
Returns
void
-
_fireRegisterEvent( definition ) → voidprivatemodule:html-support/datafilter~DataFilter#_fireRegisterEventFires
registerevent for the given element definition.Parameters
definition : HtmlSupportDataSchemaDefinition
Returns
void
-
_getCoupledAttributesMap() → Map<string, Array<string>>privatemodule:html-support/datafilter~DataFilter#_getCoupledAttributesMapCollects the map of coupled attributes. The returned map is keyed by the feature attribute name and coupled GHS attribute names are stored in the value array.
Returns
Map<string, Array<string>>
-
_registerAssociatedHtmlAttributesPostFixer() → voidprivatemodule:html-support/datafilter~DataFilter#_registerAssociatedHtmlAttributesPostFixerRemoves
html*Attributesattributes from incompatible elements.For example, consider the following HTML:
<heading2 htmlH2Attributes="...">foobar[]</heading2>Copy codePressing
entercreates a newparagraphelement that inherits thehtmlH2Attributesattribute fromheading2.<heading2 htmlH2Attributes="...">foobar</heading2> <paragraph htmlH2Attributes="...">[]</paragraph>Copy codeThis postfixer ensures that this doesn't happen, and that elements can only have
html*Attributesassociated with them, e.g.:htmlPAttributesfor<p>,htmlDivAttributesfor<div>, etc.With it enabled, pressing
enterat the end of<heading2>will create a new paragraph without thehtmlH2Attributesattribute.<heading2 htmlH2Attributes="...">foobar</heading2> <paragraph>[]</paragraph>Copy codeReturns
void
-
_registerBlockElement( definition ) → voidprivatemodule:html-support/datafilter~DataFilter#_registerBlockElementRegisters block element and attribute converters for the given data schema definition.
Parameters
definition : HtmlSupportDataSchemaBlockElementDefinition
Returns
void
-
_registerCoupledAttributesPostFixer() → voidprivatemodule:html-support/datafilter~DataFilter#_registerCoupledAttributesPostFixerRegisters a model post-fixer that is removing coupled GHS attributes of inline elements. Those attributes are removed if a coupled feature attribute is removed.
For example, consider following HTML:
<a href="foo.html" id="myId">bar</a>Copy codeWhich would be upcasted to following text node in the model:
<$text linkHref="foo.html" htmlA="{ attributes: { id: 'myId' } }">bar</$text>Copy codeWhen the user removes the link from that text (using UI), only
linkHrefattribute would be removed:<$text htmlA="{ attributes: { id: 'myId' } }">bar</$text>Copy codeThe
htmlAattribute would stay in the model and would cause GHS to generate an<a>element. This is incorrect from UX point of view, as the user wanted to remove the whole link (not onlyhref).Returns
void
-
_registerElementHandlers() → voidprivatemodule:html-support/datafilter~DataFilter#_registerElementHandlers -
_registerElementsAfterInit() → voidprivatemodule:html-support/datafilter~DataFilter#_registerElementsAfterInitRegisters elements allowed by
allowElementmethod once editor's data controller is initialized.Returns
void
-
_registerInlineElement( definition ) → voidprivatemodule:html-support/datafilter~DataFilter#_registerInlineElementRegisters inline element and attribute converters for the given data schema definition.
Extends
$textmodel schema to allow the given definition model attribute and its properties.Parameters
definition : HtmlSupportDataSchemaInlineElementDefinition
Returns
void
-
_registerObjectElement( definition ) → voidprivatemodule:html-support/datafilter~DataFilter#_registerObjectElementRegisters object element and attribute converters for the given data schema definition.
Parameters
definition : HtmlSupportDataSchemaDefinition
Returns
void
Events
-
change:isEnabled( eventInfo, name, value, oldValue )inheritedmodule:html-support/datafilter~DataFilter#event:change:isEnabledFired when the
isEnabledproperty changed value.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
isEnabled).value : booleanNew value of the
isEnabledproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
isEnabledproperty with given key ornull, if property was not set before.
-
change:{property}( eventInfo, name, value, oldValue )inheritedmodule:html-support/datafilter~DataFilter#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'Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringThe property name.
value : TValueThe new property value.
oldValue : TValueThe previous property value.
-
set:isEnabled( eventInfo, name, value, oldValue )inheritedmodule:html-support/datafilter~DataFilter#event:set:isEnabledFired when the
isEnabledproperty is going to be set but is not set yet (before thechangeevent is fired).Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
isEnabled).value : booleanNew value of the
isEnabledproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
isEnabledproperty with given key ornull, if property was not set before.
-
set:{property}( eventInfo, name, value, oldValue )inheritedmodule:html-support/datafilter~DataFilter#event:set:{property}Fired when a property value is going to be set but is not set yet (before the
changeevent is fired).You can control the final value of the property by using the event's
returnproperty.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'Copy codeNote: The event is fired even when the new value is the same as the old value.
Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringThe property name.
value : TValueThe new property value.
oldValue : TValueThe previous property value.