Done! Thank you. On Monday, August 26, 2024 at 9:41:45 AM UTC-7 mike...@chromium.org wrote:
> Also, would you remind requesting reviews for Enteprise, Debuggability, > and Testing in the chromestatus entry? Thanks! > On 8/26/24 12:40 PM, Mike Taylor wrote: > > LGTM1 to remove - if there's no usage, now is the time to get that done. > > Relevant use counter for those interested: > https://chromestatus.com/metrics/feature/timeline/popularity/5017 > On 8/26/24 12:13 PM, Chromestatus wrote: > > Contact emails sahir....@microsoft.com > > Explainer None > > Specification https://wicg.github.io/ink-enhancement > > Summary > > The attribute tells web developers how much improvement the > DelegatedInkTrails API will provide to their current ink latency. However, > this attribute is not worth increases to fingerprinting entropy. > > > Blink component Blink>Input > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInput> > > Motivation > > expectedImprovement tells web developers how much improvement the > DelegatedInkTrails API will provide to their current ink latency. However, > this attribute is not worth increases to fingerprinting entropy. The > difference in cost to the web developer between using the > expectedImprovement attribute and actually delegating the "wet" ink trail > to the OS/Browser is minimal, and upon additional discussion, there was no > good reason found for the web developer not delegating the ink trail after > receiving some value from the expectedImprovement attribute (all > improvement is good improvement). The removal of this attribute should have > minimal impact to web compatibility as it was never implemented in Blink in > the first place. This is the intent to remove the attribute from the web > exposed DelegatedInkTrailPresenter interface. There is no usage of this > attribute according to blink use counters. > > > Initial public proposal None > > TAG review None > > TAG review status Not applicable > > Risks > > > Interoperability and Compatibility > > No interoperability or compatibility risks as the feature was not > implemented and is not used; even incorrectly. > > > *Gecko*: No signal > > *WebKit*: No signal > > *Web developers*: No signals > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None > > > Debuggability > > None > > > 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 on chrome://flags None > > Finch feature name None > > Non-finch justification None > > Requires code in //chrome? False > > Tracking bug https://bugs.chromium.org/347647410 > > Estimated milestones > Shipping on desktop 130 > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5194773674328064?gate=5169972251459584 > > 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+...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0000000000006923df06209867e8%40google.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0000000000006923df06209867e8%40google.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/cb87da57-38d8-4b4b-ae8e-019947b1dc30n%40chromium.org.
