Deprecate and then remove -webkit-user-modify |
|||||||||||||||
Issue descriptionSee http://www.chromium.org/blink#launch-process for an overview of the Blink launch process. This launch issue is used for standards and implementation tracking only, not for Chrome approval regarding privacy, security, legal, UI, testing, accessibility etc. If your feature requires approval in any of those areas please additionally create a Type=Launch issue (note you will most likely want a PM to guide you through the Type=Launch process, guidance can be found at go/newchromefeature) --- Change description: Deprecate and remove -webkit-user-modify, which is a non-standard CSS property and has been rejected by CSSWG for standardization. Developers are encouraged to use contenteditable instead of -webkit-user-modify. Changes to API surface: CSS property -webkit-user-modify. Links: Public standards discussion: https://lists.w3.org/Archives/Public/www-style/2015May/0051.html Support in other browsers: Edge: Yes Firefox: No Safari: Yes ⛆ |
|
|
,
Feb 2 2017
,
Feb 3 2017
,
Feb 6 2017
,
Feb 13 2017
,
Feb 23 2017
,
Apr 28 2017
,
Aug 24 2017
Use counter collected by rbyers@: https://docs.google.com/spreadsheets/d/1w6nsJXe4g7-obbav8OpZzFF4pzjh639JShtjI08BP0Q/edit#gid=1851495891
,
Sep 12 2017
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues. We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate. For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit For any questions, please contact owencm, sshruthi, larforge
,
Oct 18 2017
,
Dec 6 2017
,
Dec 21 2017
Unassign myself as I don't have any plan to work on it.
,
Mar 3 2018
|
||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by xiaoche...@chromium.org
, Feb 1 2017