| Summary: | Unsupport -webkit-user-modify CSS property | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | HTML Editing | Assignee: | Nobody <webkit-unassigned> |
| Status: | REOPENED --- | ||
| Severity: | Enhancement | CC: | cshu, darin, efidler, enrica, hyatt, justin.garcia, mifenton, mjs, shinyak, simon.fraser, tonikitoo, tony, zcorpan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Ryosuke Niwa
2011-01-06 15:11:24 PST
Hyatt, I think you suggested this long ago. What do you think it would take to do this successfully? Any updates? :) I've seen examples of websites that rely on this feature so we can't drop this feature anytime soon. Revisiting this bug because it's causing a lot of problems in relation to UndoManager / Transaction spec. I had a discussion with Enrica, Ojan, & Tony about this, and I think we want to get some statistics on how many websites use this property. In addition, I've asked Enrica to check if there are any significant users of this property in Apple products and OS X apps. It'd be great to deprecate this property in the future. I think this Chrome use counter is relevant: WebKitUserModifyEffective 0.63% https://chromestatus.com/metrics/feature/timeline/popularity/2630 However, as far as I can tell from the code in https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/dom/element.cc;l=274?q=webkitusermodifyeffective&ss=chromium&start=31 this includes usage of the contenteditable attribute. wpt test that checks that -webkit-user-modify is not supported was added in https://github.com/web-platform-tests/wpt/pull/35471 In addition, the following spec PRs specify the HTML contenteditable="plaintext-only" which is supported in WebKit and Chromium: https://github.com/whatwg/html/pull/8275 https://github.com/w3c/editing/pull/407 |