On Wed, Jun 14, 2023 at 12:03 AM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote:
> *> **Although in the template this is phrased as a yes/no question, can > you say more about the WPT coverage and limitations?* > > > > We currently do not have tests in web-platform-tests. > > There are tests outside the external/wpt folder: > > third_party/blink/web_tests/editing/input/edit-context.html > <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/editing/input/edit-context.html> > > third_party/blink/web_tests/editing/input/edit-context-dom-mutation.html > <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/editing/input/edit-context-dom-mutation.html> > > > > I’m going to migrate as much of the contents of these as I can to WPT. > This won’t be possible for a lot of the subtests since they rely on > primitives like eventSender and textInputController, which aren’t available > in WPT. > > There is also test coverage that still needs to be written for scenarios > involving nested editable elements, and I plan to add these as WPTs. > Would it be possible to add WebDriver extensions to enable these tests to move over to WPT? +Mathias Bynens <m...@google.com> - FYI > > > There’s been some work done > <https://chromium-review.googlesource.com/c/chromium/src/+/3009937> > around adding support for IME testing but my understanding is that more > work is needed in order to use this in WPTs. > > > > *From:* Daniel Clark > *Sent:* Tuesday, June 13, 2023 10:42 AM > *To:* Mike Taylor <miketa...@chromium.org>; blink-dev@chromium.org > *Cc:* Chris Harrelson <chris...@google.com>; Anupam Snigdha < > sni...@microsoft.com>; Alex Keng <shih...@microsoft.com> > *Subject:* RE: [blink-dev] Intent to Experiment: EditContext API > > > > Tentatively M116 - M120 for the trial. > > > > *From:* Mike Taylor <miketa...@chromium.org> > *Sent:* Tuesday, June 13, 2023 9:24 AM > *To:* Daniel Clark <dan...@microsoft.com>; blink-dev@chromium.org > *Cc:* Chris Harrelson <chris...@google.com>; Anupam Snigdha < > sni...@microsoft.com>; Alex Keng <shih...@microsoft.com> > *Subject:* Re: [blink-dev] Intent to Experiment: EditContext API > > > > Do you all have a timeline in mind for experimentation? > > On 6/12/23 7:00 PM, 'Daniel Clark' via blink-dev wrote: > > Contact emails > > sni...@microsoft.com, shih...@microsoft.com, bemat...@microsoft.com, > dan...@microsoft.com > > > Explainer > > https://github.com/w3c/edit-context/blob/gh-pages/explainer.md > > > Specification > > https://w3c.github.io/edit-context > > > Design docs > > > https://github.com/w3c/edit-context/blob/gh-pages/dev-design.md > > > Summary > > The EditContext API simplifies the process of integrating a web app with > advanced text input methods such as VK shape-writing, Handwriting panels, > speech recognition, IME Compositions etc., improves accessibility and > performance, and unlocks new capabilities for web-based editors. > > > > > Blink component > > Blink>Editing > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EEditing> > > > Search tags > > editing <https://chromestatus.com/features#tags:editing>, contenteditable > <https://chromestatus.com/features#tags:contenteditable>, input > <https://chromestatus.com/features#tags:input>, rawinput > <https://chromestatus.com/features#tags:rawinput>, ime > <https://chromestatus.com/features#tags:ime> > > > TAG review > > https://github.com/w3ctag/design-reviews/issues/416 > > > TAG review status > > Pending > > > Risks > > > > > Interoperability and Compatibility > > There are no known interop or compat risks. > > > > *Gecko*: No signal > > *WebKit*: No signal > > It'd be good to file for positions (even if that doesn't block an OT) > > *Web developers*: Strongly positive Positive feedback from Word online, > Adobe and Figma, Google Docs > > *Other signals*: > > > Activation > > Developers interested in this feature will typically have their own > polyfill for text input using hidden textarea or contenteditable elements. > Feature detecting and using new API to avoid side effects of previous > approaches is intended to be easily adoptable. > > Do we plan for each property that adopts this to write their own polyfill? Or to split their code paths for supporting and non supporting browsers? > > > > WebView application risks > > None > Goals for experimentation > > We are looking for feedback on the developer ergonomics of using the API > and for confirmation that it meets the needs of production web apps for > various input modes. This is a complex API, and different developers are > expected to use it in different ways. For example, some partners plan to > construct the view of their editable region in the subtree of the > EditContext-associated element, while other partners plan to keep the > EditContext-associated element off-screen while using the EditContext APIs > to set the bounds of the editable region. > > > > We want to ensure that our design enables all these scenarios and is > robust given the wide field of IMEs utilized by different users, which may > have subtly different behaviors and event timings. > > > Ongoing technical constraints > > None > > > > > Debuggability > > Existing DevTools functionality should suffice to debug EditContext. > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > Yes > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > No > > > Flag name > > --enable-blink-features=EditContext > > > Requires code in //chrome? > > False > > > Tracking bug > > https://bugs.chromium.org/p/chromium/issues/detail?id=999184 > > > Estimated milestones > > No milestones specified > > > > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5041440373604352 > > > Links to previous Intent discussions > > I2I: > https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/OHqvPx9mFww/m/1za_qdEHDwAJ > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN6PR00MB0448C960D827BFAFE2FD1F2CC554A%40SN6PR00MB0448.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SN6PR00MB0448C960D827BFAFE2FD1F2CC554A%40SN6PR00MB0448.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DM5PR00MB04395FA5C89C3CAA7066A42CC555A%40DM5PR00MB0439.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DM5PR00MB04395FA5C89C3CAA7066A42CC555A%40DM5PR00MB0439.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXYev0F0v3QE7JnuDGimWbyBBkJ6a8nk5knuoJLF-GxGQ%40mail.gmail.com.
