Browse Source

Docs: Adjusted to recent UI refactor.

Krzysztof Krztoń 6 years ago
parent
commit
74cad7fb8a

+ 2 - 2
docs/builds/guides/frameworks/angular.md

@@ -83,9 +83,9 @@ export class MyComponent {
 	public Editor = DecoupledEditor;
 
 	public onReady( editor ) {
-		editor.ui.view.editable.element.parentElement.insertBefore(
+		editor.ui.getEditableElement().parentElement.insertBefore(
 			editor.ui.view.toolbar.element,
-			editor.ui.view.editable.element
+			editor.ui.getEditableElement()
 		);
 	}
 }

+ 2 - 2
docs/builds/guides/frameworks/react.md

@@ -134,9 +134,9 @@ class App extends Component {
                         console.log( 'Editor is ready to use!', editor );
 
                         // Insert the toolbar before the editable area.
-                        editor.ui.view.editable.element.parentElement.insertBefore(
+                        editor.ui.getEditableElement().parentElement.insertBefore(
                             editor.ui.view.toolbar.element,
-                            editor.ui.view.editable.element
+                            editor.ui.getEditableElement()
                         );
                     } }
                     onChange={ ( event, editor ) => console.log( { event, editor } ) }

+ 3 - 3
docs/builds/guides/frameworks/vuejs.md

@@ -368,9 +368,9 @@ Since accessing the editor toolbar is not possible until after the editor instan
 		methods: {
 			onReady( editor )  {
 				// Insert the toolbar before the editable area.
-				editor.ui.view.editable.element.parentElement.insertBefore(
+				editor.ui.getEditableElement().parentElement.insertBefore(
 					editor.ui.view.toolbar.element,
-					editor.ui.view.editable.element
+					editor.ui.getEditableElement()
 				);
 			}
 		}
@@ -413,7 +413,7 @@ This directive specifies the editor to be used by the component. It must directl
 
 ### `tag-name`
 
-By default, the editor component creates a `<div>` container which is used as an element passed to the editor (e.g. {@link module:editor-classic/classiceditor~ClassicEditor#element `ClassicEditor#element`}). The element can be configured, so for example to create a `<textarea>`, use the following directive:
+By default, the editor component creates a `<div>` container which is used as an element passed to the editor (e.g. {@link module:editor-classic/classiceditorui~ClassicEditorUI#element `ClassicEditor#element`}). The element can be configured, so for example to create a `<textarea>`, use the following directive:
 
 ```html
 <ckeditor :editor="editor" tag-name="textarea"></ckeditor>

+ 1 - 1
docs/builds/guides/migrate.md

@@ -211,7 +211,7 @@ Note: The number of options was reduced on purpose. We understood that configuri
 			<td><a href="/docs/ckeditor4/latest/api/CKEDITOR_config.html#cfg-disableNativeSpellChecker">disableNativeSpellChecker</a></td>
 			<td>
 				<p>Unavailable, however, in case of Inline and Balloon editors can be done by setting the <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/spellcheck" target="_blank" rel="noopener"><code>spellcheck</code></a> attribute directly on the element where CKEditor should be enabled.</p>
-				<p>For Classic editor, call <code>editor.ui.view.editable.editableElement.setAttribute(&apos;spellcheck&apos;, &apos;false&apos;);</code> after creating the editor.</p>
+				<p>For Classic editor, call <code>editor.ui.getEditableElement().setAttribute(&apos;spellcheck&apos;, &apos;false&apos;);</code> after creating the editor.</p>
 			</td>
 		</tr>
 		<tr>

+ 1 - 1
docs/framework/guides/architecture/ui-library.md

@@ -191,7 +191,7 @@ Similarly, when rendered, the template also takes care of DOM events. A binding
 
 Views are organized into {@link module:ui/viewcollection~ViewCollection collections} which manage their elements and propagate DOM events even further. Adding or removing a view in a collection moves the {@link module:ui/view~View#element view's element} in the DOM to reflect the position.
 
-Each editor UI has a {@link module:core/editor/editorui~EditorUI#view root view}, which can be found under `editor.ui.view`. Such view usually defines the container element of the editor and undermost view collections that other features can populate.
+Each editor UI has a `root view` (e.g. {@link e.g. {@link module:editor-classic/classiceditorui~ClassicEditorUI#view `ClassicEditor#view`}), which can be found under `editor.ui.view`. Such view usually defines the container element of the editor and undermost view collections that other features can populate.
 
 For instance, the `BoxedEditorUiView` class defines two collections:
 * {@link module:ui/editorui/boxed/boxededitoruiview~BoxedEditorUIView#top} &ndash; A collection that hosts the toolbar.