@ckeditor/ckeditor5-editor-classic 48.2.0-alpha.7 → 48.3.0-alpha.0

package/dist/classiceditor.d.ts

@@ -1,234 +1,234 @@
 /**
- * @license Copyright (c) 2003-2026, CKSource Holding sp. z o.o. All rights reserved.
- * For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-licensing-options
- */
-import { ClassicEditorUI } from './classiceditorui.js';
-import { Editor, type EditorConfig } from '@ckeditor/ckeditor5-core';
-declare const ClassicEditor_base: import("@ckeditor/ckeditor5-utils").Mixed<typeof Editor, import("@ckeditor/ckeditor5-core").ElementApi>;
+* @license Copyright (c) 2003-2026, CKSource Holding sp. z o.o. All rights reserved.
+* For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-licensing-options
+*/
+import { ClassicEditorUI } from "./classiceditorui.js";
+import { Editor, type EditorConfig, type ElementApiMixinConstructor } from "@ckeditor/ckeditor5-core";
+declare const ClassicEditorBase: ElementApiMixinConstructor<typeof Editor>;
 /**
- * The classic editor implementation. It uses an inline editable and a sticky toolbar, all enclosed in a boxed UI.
- * See the {@glink examples/builds/classic-editor demo}.
- *
- * In order to create a classic editor instance, use the static
- * {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`} method.
- */
-export declare class ClassicEditor extends /* #__PURE__ */ ClassicEditor_base {
-    /**
-     * @inheritDoc
-     */
-    static get editorName(): 'ClassicEditor';
-    /**
-     * @inheritDoc
-     */
-    readonly ui: ClassicEditorUI;
-    /**
-     * Creates an instance of the classic editor.
-     *
-     * **Note:** do not use the constructor to create editor instances. Use the static
-     * {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`} method instead.
-     *
-     * @param config The editor configuration.
-     */
-    protected constructor(config: EditorConfig);
-    /**
-     * Creates an instance of the classic editor.
-     *
-     * **Note:** do not use the constructor to create editor instances. Use the static
-     * {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`} method instead.
-     *
-     * **Note**: This constructor signature is deprecated and will be removed in the future release.
-     *
-     * @deprecated
-     * @param sourceElementOrData The DOM element that will be the source for the created editor
-     * or the editor's initial data. For more information see
-     * {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`}.
-     * @param config The editor configuration.
-     */
-    protected constructor(sourceElementOrData: HTMLElement | string, config: EditorConfig);
-    /**
-     * Destroys the editor instance, releasing all resources used by it.
-     *
-     * Updates the original editor element with the data if the
-     * {@link module:core/editor/editorconfig~EditorConfig#updateSourceElementOnDestroy `updateSourceElementOnDestroy`}
-     * configuration option is set to `true`.
-     */
-    destroy(): Promise<unknown>;
-    /**
-     * Creates a new classic editor instance.
-     *
-     * There are three ways how the editor can be initialized.
-     *
-     * # Replacing a DOM element (and loading data from it)
-     *
-     * You can initialize the editor using an existing DOM element:
-     *
-     * ```ts
-     * ClassicEditor
-     * 	.create( {
-     * 		attachTo: document.querySelector( '#editor' )
-     * 	} )
-     * 	.then( editor => {
-     * 		console.log( 'Editor was initialized', editor );
-     * 	} )
-     * 	.catch( err => {
-     * 		console.error( err.stack );
-     * 	} );
-     * ```
-     *
-     * The element's content will be used as the editor data and the element will be replaced by the editor UI.
-     *
-     * # Creating a detached editor
-     *
-     * Alternatively, you can initialize the editor by passing the initial data directly as a string.
-     * In this case, the editor will render an element that must be inserted into the DOM:
-     *
-     * ```ts
-     * ClassicEditor
-     * 	.create( {
-     * 		root: {
-     * 			initialData: '<p>Hello world!</p>'
-     * 		}
-     * 	} )
-     * 	.then( editor => {
-     * 		console.log( 'Editor was initialized', editor );
-     *
-     * 		// Initial data was provided so the editor UI element needs to be added manually to the DOM.
-     * 		document.body.appendChild( editor.ui.element );
-     * 	} )
-     * 	.catch( err => {
-     * 		console.error( err.stack );
-     * 	} );
-     * ```
-     *
-     * This lets you dynamically append the editor to your web page whenever it is convenient for you. You may use this method if your
-     * web page content is generated on the client side and the DOM structure is not ready at the moment when you initialize the editor.
-     *
-     * # Replacing a DOM element (and data provided in `config.root.initialData`)
-     *
-     * You can also mix these two ways by providing a DOM element to be used and passing the initial data through the configuration:
-     *
-     * ```ts
-     * ClassicEditor
-     * 	.create( {
-     * 		attachTo: document.querySelector( '#editor' ),
-     * 		root: {
-     * 			initialData: '<p>Hello world!</p>'
-     * 		}
-     * 	} )
-     * 	.then( editor => {
-     * 		console.log( 'Editor was initialized', editor );
-     * 	} )
-     * 	.catch( err => {
-     * 		console.error( err.stack );
-     * 	} );
-     * ```
-     *
-     * This method can be used to initialize the editor on an existing element with the specified content in case if your integration
-     * makes it difficult to set the content of the source element.
-     *
-     * # Configuring the editor
-     *
-     * See the {@link module:core/editor/editorconfig~EditorConfig editor configuration documentation} to learn more about
-     * customizing plugins, toolbar and more.
-     *
-     * @param config The editor configuration.
-     * @returns A promise resolved once the editor is ready. The promise resolves with the created editor instance.
-     */
-    static create(config: EditorConfig): Promise<ClassicEditor>;
-    /**
-     * Creates a new classic editor instance.
-     *
-     * **Note**: This method signature is deprecated and will be removed in the future release.
-     *
-     * There are three ways how the editor can be initialized.
-     *
-     * # Replacing a DOM element (and loading data from it)
-     *
-     * You can initialize the editor using an existing DOM element:
-     *
-     * ```ts
-     * ClassicEditor
-     * 	.create( document.querySelector( '#editor' ) )
-     * 	.then( editor => {
-     * 		console.log( 'Editor was initialized', editor );
-     * 	} )
-     * 	.catch( err => {
-     * 		console.error( err.stack );
-     * 	} );
-     * ```
-     *
-     * The element's content will be used as the editor data and the element will be replaced by the editor UI.
-     *
-     * # Creating a detached editor
-     *
-     * Alternatively, you can initialize the editor by passing the initial data directly as a string.
-     * In this case, the editor will render an element that must be inserted into the DOM:
-     *
-     * ```ts
-     * ClassicEditor
-     * 	.create( '<p>Hello world!</p>' )
-     * 	.then( editor => {
-     * 		console.log( 'Editor was initialized', editor );
-     *
-     * 		// Initial data was provided so the editor UI element needs to be added manually to the DOM.
-     * 		document.body.appendChild( editor.ui.element );
-     * 	} )
-     * 	.catch( err => {
-     * 		console.error( err.stack );
-     * 	} );
-     * ```
-     *
-     * This lets you dynamically append the editor to your web page whenever it is convenient for you. You may use this method if your
-     * web page content is generated on the client side and the DOM structure is not ready at the moment when you initialize the editor.
-     *
-     * # Replacing a DOM element (and data provided in `config.root.initialData`)
-     *
-     * You can also mix these two ways by providing a DOM element to be used and passing the initial data through the configuration:
-     *
-     * ```ts
-     * ClassicEditor
-     * 	.create( document.querySelector( '#editor' ), {
-     * 		root: {
-     * 			initialData: '<p>Hello world!</p>'
-     * 		}
-     * 	} )
-     * 	.then( editor => {
-     * 		console.log( 'Editor was initialized', editor );
-     * 	} )
-     * 	.catch( err => {
-     * 		console.error( err.stack );
-     * 	} );
-     * ```
-     *
-     * This method can be used to initialize the editor on an existing element with the specified content in case if your integration
-     * makes it difficult to set the content of the source element.
-     *
-     * Note that an error will be thrown if you pass the initial data both as the first parameter and also in the configuration.
-     *
-     * # Configuring the editor
-     *
-     * See the {@link module:core/editor/editorconfig~EditorConfig editor configuration documentation} to learn more about
-     * customizing plugins, toolbar and more.
-     *
-     * @deprecated
-     * @param sourceElementOrData The DOM element that will be the source for the created editor
-     * or the editor's initial data.
-     *
-     * If a DOM element is passed, its content will be automatically loaded to the editor upon initialization
-     * and the {@link module:editor-classic/classiceditorui~ClassicEditorUI#element editor element} will replace the passed element
-     * in the DOM (the original one will be hidden and the editor will be injected next to it).
-     *
-     * If the {@link module:core/editor/editorconfig~EditorConfig#updateSourceElementOnDestroy updateSourceElementOnDestroy}
-     * option is set to `true`, the editor data will be set back to the original element once the editor is destroyed and when a form,
-     * in which this element is contained, is submitted (if the original element is a `<textarea>`). This ensures seamless integration
-     * with native web forms.
-     *
-     * If the initial data is passed, a detached editor will be created. In this case you need to insert it into the DOM manually.
-     * It is available under the {@link module:editor-classic/classiceditorui~ClassicEditorUI#element `editor.ui.element`} property.
-     *
-     * @param config The editor configuration.
-     * @returns A promise resolved once the editor is ready. The promise resolves with the created editor instance.
-     */
-    static create(sourceElementOrData: HTMLElement | string, config: EditorConfig): Promise<ClassicEditor>;
+* The classic editor implementation. It uses an inline editable and a sticky toolbar, all enclosed in a boxed UI.
+* See the {@glink examples/builds/classic-editor demo}.
+*
+* In order to create a classic editor instance, use the static
+* {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`} method.
+*/
+export declare class ClassicEditor extends ClassicEditorBase {
+	/**
+	* @inheritDoc
+	*/
+	static override get editorName(): "ClassicEditor";
+	/**
+	* @inheritDoc
+	*/
+	readonly ui: ClassicEditorUI;
+	/**
+	* Creates an instance of the classic editor.
+	*
+	* **Note:** do not use the constructor to create editor instances. Use the static
+	* {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`} method instead.
+	*
+	* @param config The editor configuration.
+	*/
+	protected constructor(config: EditorConfig);
+	/**
+	* Creates an instance of the classic editor.
+	*
+	* **Note:** do not use the constructor to create editor instances. Use the static
+	* {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`} method instead.
+	*
+	* **Note**: This constructor signature is deprecated and will be removed in the future release.
+	*
+	* @deprecated
+	* @param sourceElementOrData The DOM element that will be the source for the created editor
+	* or the editor's initial data. For more information see
+	* {@link module:editor-classic/classiceditor~ClassicEditor.create `ClassicEditor.create()`}.
+	* @param config The editor configuration.
+	*/
+	protected constructor(sourceElementOrData: HTMLElement | string, config: EditorConfig);
+	/**
+	* Destroys the editor instance, releasing all resources used by it.
+	*
+	* Updates the original editor element with the data if the
+	* {@link module:core/editor/editorconfig~EditorConfig#updateSourceElementOnDestroy `updateSourceElementOnDestroy`}
+	* configuration option is set to `true`.
+	*/
+	override destroy(): Promise<unknown>;
+	/**
+	* Creates a new classic editor instance.
+	*
+	* There are three ways how the editor can be initialized.
+	*
+	* # Replacing a DOM element (and loading data from it)
+	*
+	* You can initialize the editor using an existing DOM element:
+	*
+	* ```ts
+	* ClassicEditor
+	* 	.create( {
+	* 		attachTo: document.querySelector( '#editor' )
+	* 	} )
+	* 	.then( editor => {
+	* 		console.log( 'Editor was initialized', editor );
+	* 	} )
+	* 	.catch( err => {
+	* 		console.error( err.stack );
+	* 	} );
+	* ```
+	*
+	* The element's content will be used as the editor data and the element will be replaced by the editor UI.
+	*
+	* # Creating a detached editor
+	*
+	* Alternatively, you can initialize the editor by passing the initial data directly as a string.
+	* In this case, the editor will render an element that must be inserted into the DOM:
+	*
+	* ```ts
+	* ClassicEditor
+	* 	.create( {
+	* 		root: {
+	* 			initialData: '<p>Hello world!</p>'
+	* 		}
+	* 	} )
+	* 	.then( editor => {
+	* 		console.log( 'Editor was initialized', editor );
+	*
+	* 		// Initial data was provided so the editor UI element needs to be added manually to the DOM.
+	* 		document.body.appendChild( editor.ui.element );
+	* 	} )
+	* 	.catch( err => {
+	* 		console.error( err.stack );
+	* 	} );
+	* ```
+	*
+	* This lets you dynamically append the editor to your web page whenever it is convenient for you. You may use this method if your
+	* web page content is generated on the client side and the DOM structure is not ready at the moment when you initialize the editor.
+	*
+	* # Replacing a DOM element (and data provided in `config.root.initialData`)
+	*
+	* You can also mix these two ways by providing a DOM element to be used and passing the initial data through the configuration:
+	*
+	* ```ts
+	* ClassicEditor
+	* 	.create( {
+	* 		attachTo: document.querySelector( '#editor' ),
+	* 		root: {
+	* 			initialData: '<p>Hello world!</p>'
+	* 		}
+	* 	} )
+	* 	.then( editor => {
+	* 		console.log( 'Editor was initialized', editor );
+	* 	} )
+	* 	.catch( err => {
+	* 		console.error( err.stack );
+	* 	} );
+	* ```
+	*
+	* This method can be used to initialize the editor on an existing element with the specified content in case if your integration
+	* makes it difficult to set the content of the source element.
+	*
+	* # Configuring the editor
+	*
+	* See the {@link module:core/editor/editorconfig~EditorConfig editor configuration documentation} to learn more about
+	* customizing plugins, toolbar and more.
+	*
+	* @param config The editor configuration.
+	* @returns A promise resolved once the editor is ready. The promise resolves with the created editor instance.
+	*/
+	static override create(config: EditorConfig): Promise<ClassicEditor>;
+	/**
+	* Creates a new classic editor instance.
+	*
+	* **Note**: This method signature is deprecated and will be removed in the future release.
+	*
+	* There are three ways how the editor can be initialized.
+	*
+	* # Replacing a DOM element (and loading data from it)
+	*
+	* You can initialize the editor using an existing DOM element:
+	*
+	* ```ts
+	* ClassicEditor
+	* 	.create( document.querySelector( '#editor' ) )
+	* 	.then( editor => {
+	* 		console.log( 'Editor was initialized', editor );
+	* 	} )
+	* 	.catch( err => {
+	* 		console.error( err.stack );
+	* 	} );
+	* ```
+	*
+	* The element's content will be used as the editor data and the element will be replaced by the editor UI.
+	*
+	* # Creating a detached editor
+	*
+	* Alternatively, you can initialize the editor by passing the initial data directly as a string.
+	* In this case, the editor will render an element that must be inserted into the DOM:
+	*
+	* ```ts
+	* ClassicEditor
+	* 	.create( '<p>Hello world!</p>' )
+	* 	.then( editor => {
+	* 		console.log( 'Editor was initialized', editor );
+	*
+	* 		// Initial data was provided so the editor UI element needs to be added manually to the DOM.
+	* 		document.body.appendChild( editor.ui.element );
+	* 	} )
+	* 	.catch( err => {
+	* 		console.error( err.stack );
+	* 	} );
+	* ```
+	*
+	* This lets you dynamically append the editor to your web page whenever it is convenient for you. You may use this method if your
+	* web page content is generated on the client side and the DOM structure is not ready at the moment when you initialize the editor.
+	*
+	* # Replacing a DOM element (and data provided in `config.root.initialData`)
+	*
+	* You can also mix these two ways by providing a DOM element to be used and passing the initial data through the configuration:
+	*
+	* ```ts
+	* ClassicEditor
+	* 	.create( document.querySelector( '#editor' ), {
+	* 		root: {
+	* 			initialData: '<p>Hello world!</p>'
+	* 		}
+	* 	} )
+	* 	.then( editor => {
+	* 		console.log( 'Editor was initialized', editor );
+	* 	} )
+	* 	.catch( err => {
+	* 		console.error( err.stack );
+	* 	} );
+	* ```
+	*
+	* This method can be used to initialize the editor on an existing element with the specified content in case if your integration
+	* makes it difficult to set the content of the source element.
+	*
+	* Note that an error will be thrown if you pass the initial data both as the first parameter and also in the configuration.
+	*
+	* # Configuring the editor
+	*
+	* See the {@link module:core/editor/editorconfig~EditorConfig editor configuration documentation} to learn more about
+	* customizing plugins, toolbar and more.
+	*
+	* @deprecated
+	* @param sourceElementOrData The DOM element that will be the source for the created editor
+	* or the editor's initial data.
+	*
+	* If a DOM element is passed, its content will be automatically loaded to the editor upon initialization
+	* and the {@link module:editor-classic/classiceditorui~ClassicEditorUI#element editor element} will replace the passed element
+	* in the DOM (the original one will be hidden and the editor will be injected next to it).
+	*
+	* If the {@link module:core/editor/editorconfig~EditorConfig#updateSourceElementOnDestroy updateSourceElementOnDestroy}
+	* option is set to `true`, the editor data will be set back to the original element once the editor is destroyed and when a form,
+	* in which this element is contained, is submitted (if the original element is a `<textarea>`). This ensures seamless integration
+	* with native web forms.
+	*
+	* If the initial data is passed, a detached editor will be created. In this case you need to insert it into the DOM manually.
+	* It is available under the {@link module:editor-classic/classiceditorui~ClassicEditorUI#element `editor.ui.element`} property.
+	*
+	* @param config The editor configuration.
+	* @returns A promise resolved once the editor is ready. The promise resolves with the created editor instance.
+	*/
+	static override create(sourceElementOrData: HTMLElement | string, config: EditorConfig): Promise<ClassicEditor>;
 }
 export {};

package/dist/classiceditorui.d.ts

@@ -1,82 +1,82 @@
 /**
- * @license Copyright (c) 2003-2026, CKSource Holding sp. z o.o. All rights reserved.
- * For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-licensing-options
- */
+* @license Copyright (c) 2003-2026, CKSource Holding sp. z o.o. All rights reserved.
+* For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-licensing-options
+*/
 /**
- * @module editor-classic/classiceditorui
- */
-import { type Editor } from '@ckeditor/ckeditor5-core';
-import { EditorUI } from '@ckeditor/ckeditor5-ui';
-import { type ClassicEditorUIView } from './classiceditoruiview.js';
+* @module editor-classic/classiceditorui
+*/
+import { type Editor } from "@ckeditor/ckeditor5-core";
+import { EditorUI } from "@ckeditor/ckeditor5-ui";
+import { type ClassicEditorUIView } from "./classiceditoruiview.js";
 /**
- * The classic editor UI class.
- */
+* The classic editor UI class.
+*/
 export declare class ClassicEditorUI extends EditorUI {
-    /**
-     * The main (top–most) view of the editor UI.
-     */
-    readonly view: ClassicEditorUIView;
-    /**
-     * A normalized `config.toolbar` object.
-     */
-    private readonly _toolbarConfig;
-    /**
-     * The element replacer instance used to hide the editor's source element.
-     */
-    private readonly _elementReplacer;
-    /**
-     * Creates an instance of the classic editor UI class.
-     *
-     * @param editor The editor instance.
-     * @param view The view of the UI.
-     */
-    constructor(editor: Editor, view: ClassicEditorUIView);
-    /**
-     * @inheritDoc
-     */
-    get element(): HTMLElement | null;
-    /**
-     * Initializes the UI.
-     *
-     * @param replacementElement The DOM element that will be the source for the created editor.
-     */
-    init(replacementElement: HTMLElement | null): void;
-    /**
-     * @inheritDoc
-     */
-    destroy(): void;
-    /**
-     * Initializes the editor toolbar.
-     */
-    private _initToolbar;
-    /**
-     * Enable the placeholder text on the editing root.
-     */
-    private _initPlaceholder;
-    /**
-     * Provides an integration between the sticky toolbar and {@link module:ui/panel/balloon/contextualballoon contextual balloon plugin}.
-     * It allows the contextual balloon to consider the height of the
-     * {@link module:editor-classic/classiceditoruiview~ClassicEditorUIView#stickyPanel}. It prevents the balloon from overlapping
-     * the sticky toolbar by adjusting the balloon's position using viewport offset configuration.
-     */
-    private _initContextualBalloonIntegration;
-    /**
-     * Provides an integration between the sticky toolbar and {@link module:utils/dom/scroll~scrollViewportToShowTarget}.
-     * It allows the UI-agnostic engine method to consider the geometry of the
-     * {@link module:editor-classic/classiceditoruiview~ClassicEditorUIView#stickyPanel} that pins to the
-     * edge of the viewport and can obscure the user caret after scrolling the window.
-     *
-     * @param evt The `scrollToTheSelection` event info.
-     * @param data The payload carried by the `scrollToTheSelection` event.
-     * @param originalArgs The original arguments passed to `scrollViewportToShowTarget()` method (see implementation to learn more).
-     */
-    private _handleScrollToTheSelectionWithStickyPanel;
-    /**
-     * Provides an integration between the sticky toolbar and {@link module:ui/dialog/dialog the Dialog plugin}.
-     *
-     * It moves the dialog down to ensure that the
-     * {@link module:editor-classic/classiceditoruiview~ClassicEditorUIView#stickyPanel sticky panel}
-     * used by the editor UI will not get obscured by the dialog when the dialog uses one of its automatic positions.
-     */
-    private _initDialogPluginIntegration;
+	/**
+	* The main (top–most) view of the editor UI.
+	*/
+	readonly view: ClassicEditorUIView;
+	/**
+	* A normalized `config.toolbar` object.
+	*/
+	private readonly _toolbarConfig;
+	/**
+	* The element replacer instance used to hide the editor's source element.
+	*/
+	private readonly _elementReplacer;
+	/**
+	* Creates an instance of the classic editor UI class.
+	*
+	* @param editor The editor instance.
+	* @param view The view of the UI.
+	*/
+	constructor(editor: Editor, view: ClassicEditorUIView);
+	/**
+	* @inheritDoc
+	*/
+	override get element(): HTMLElement | null;
+	/**
+	* Initializes the UI.
+	*
+	* @param replacementElement The DOM element that will be the source for the created editor.
+	*/
+	init(replacementElement: HTMLElement | null): void;
+	/**
+	* @inheritDoc
+	*/
+	override destroy(): void;
+	/**
+	* Initializes the editor toolbar.
+	*/
+	private _initToolbar;
+	/**
+	* Enable the placeholder text on the editing root.
+	*/
+	private _initPlaceholder;
+	/**
+	* Provides an integration between the sticky toolbar and {@link module:ui/panel/balloon/contextualballoon contextual balloon plugin}.
+	* It allows the contextual balloon to consider the height of the
+	* {@link module:editor-classic/classiceditoruiview~ClassicEditorUIView#stickyPanel}. It prevents the balloon from overlapping
+	* the sticky toolbar by adjusting the balloon's position using viewport offset configuration.
+	*/
+	private _initContextualBalloonIntegration;
+	/**
+	* Provides an integration between the sticky toolbar and {@link module:utils/dom/scroll~scrollViewportToShowTarget}.
+	* It allows the UI-agnostic engine method to consider the geometry of the
+	* {@link module:editor-classic/classiceditoruiview~ClassicEditorUIView#stickyPanel} that pins to the
+	* edge of the viewport and can obscure the user caret after scrolling the window.
+	*
+	* @param evt The `scrollToTheSelection` event info.
+	* @param data The payload carried by the `scrollToTheSelection` event.
+	* @param originalArgs The original arguments passed to `scrollViewportToShowTarget()` method (see implementation to learn more).
+	*/
+	private _handleScrollToTheSelectionWithStickyPanel;
+	/**
+	* Provides an integration between the sticky toolbar and {@link module:ui/dialog/dialog the Dialog plugin}.
+	*
+	* It moves the dialog down to ensure that the
+	* {@link module:editor-classic/classiceditoruiview~ClassicEditorUIView#stickyPanel sticky panel}
+	* used by the editor UI will not get obscured by the dialog when the dialog uses one of its automatic positions.
+	*/
+	private _initDialogPluginIntegration;
 }