8
0
Maciej Gołaszewski 7 лет назад
Родитель
Сommit
b5f113d8e1
2 измененных файлов с 6 добавлено и 15 удалено
  1. 3 1
      docs/builds/guides/faq.md
  2. 3 14
      docs/builds/guides/support/browser-compatibility.md

+ 3 - 1
docs/builds/guides/faq.md

@@ -81,7 +81,9 @@ Image features are enabled by default in all editor builds (also the image uploa
 
 ## How to use CKEditor 5 with frameworks (Angular, React, etc.)?
 
-There are no ready–to–use framework adapters as of yet. We recognize the popularity of these frameworks and our intention is for the guides and seamless integrations to be developed in the future. Meanwhile, please refer to the [GitHub issue](https://github.com/ckeditor/ckeditor5/issues/599) for more information.
+The beta versions of official [Angular](https://github.com/ckeditor/ckeditor5-angular) and [React](https://github.com/ckeditor/ckeditor5-react) integrations are already available to try out and test. Your feedback will be most welcome!
+
+We will be working on further integrations (and documentation) soon. Meanwhile, please refer to the dedicated [GitHub issue](https://github.com/ckeditor/ckeditor5/issues/599) for more information.
 
 ## How to get a fully–featured editor build (a.k.a. CKEditor 4 "Full Package")?
 

+ 3 - 14
docs/builds/guides/support/browser-compatibility.md

@@ -38,21 +38,10 @@ Features known to not be fully supported yet:
 
 ## Mobile environment
 
-Although CKEditor 5 works in Safari for iOS and Chrome for Android, it has not been fully tested yet and there are known bugs and inconveniences. Full support for mobile browsers will be our goal after releasing v10.0.0.
+CKEditor 5 is currently supported in the following mobile environments:
 
-When working on mobile support we need to consider two complex aspects:
-
-* **Special UI, designed for mobile.**
-
-	During the design phase we understood that creating a responsive and touch-friendly UI will not guarantee a desired UX level by itself. Also, that the "mobile first" approach has no application in this case due to constraints of the mobile environment and the specific editing method. Therefore, we plan to introduce a completely customized, mobile-oriented UI.
-
-	We began research on how to display necessary UI controls on the screen and, sadly, it turned out that mobile Safari's viewport mechanics makes it extremely complicated to display the UI in a reliable way. You can read more in the [UX: Mobile editing](https://github.com/ckeditor/ckeditor5-design/issues/149) ticket.
-
-* **Handling mobile browsers' quirks.**
-
-	Mobile browsers (especially mobile Safari) work differently than their desktop equivalents. [Chrome's incomplete `keydown` event](https://bugs.chromium.org/p/chromium/issues/detail?id=118639) is just one of the issues that we need to deal with.
-
-	For several years we have worked with W3C on [fixing `contentEditable`](https://medium.com/content-uneditable/fixing-contenteditable-1a9a5073c35d) — a technology on which the entire browser-based editing is based. Recently, browser vendors started implementing the core part of [the new specifications](http://w3c.github.io/editing/) — the `beforeinput` event which has a chance to improve the situation. CKEditor 5's architecture was designed with this event in mind, so we will start taking advantage of it as soon as it proves to be stable enough.
+* Android (all vendor-supported versions)
+* iOS (all vendor-supported versions)
 
 ## Quality assurance