Alternative implementation suggestion for web developers
No alternative. Developers needs to make appearances with their own way.
Usage information from UseCounter
https://www.chromestatus.com/metrics/feature/timeline/popularity/2560Link to entry on the Chrome Platform Status
Requesting approval to remove too?
--
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/accc7efc-20c4-4d35-806b-78c0fede1ca0%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8XCOczW6iOOKrZhvfp%2BhSggWpw02pOLHfKjyYR88WOkQ%40mail.gmail.com.
Hi tkent!This looks like a nice cleanup and for all but two the usage numbers are so low that there is no reason to worry, but there are two that are a bit higher.https://www.chromestatus.com/metrics/feature/timeline/popularity/2774 - for things that are not buttons but want to look like buttons. What is the worst case scenario here? What happens if this appearance disappears?
https://www.chromestatus.com/metrics/feature/timeline/popularity/2579 - search that are not really search. What is the worst case scenario here? Is it just that the cross button stops being available in a text field or is there more to it?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.z4r4tjhjrbppqq%40cicero2.linkoping.osa.
On Fri, Jul 12, 2019 at 5:07 AM Daniel Bratell <bra...@opera.com> wrote:Hi tkent!This looks like a nice cleanup and for all but two the usage numbers are so low that there is no reason to worry, but there are two that are a bit higher.https://www.chromestatus.com/metrics/feature/timeline/popularity/2774 - for things that are not buttons but want to look like buttons. What is the worst case scenario here? What happens if this appearance disappears?I'd like to categorize this into three use cases:a) Drop-down box <select> with 'button' appearanceb) Hyper-link <a href="..."> with 'button' appearance; https://www.chromestatus.com/metrics/feature/timeline/popularity/1470c) Others; e.g. <div> with 'button' appearanceIn any case, an element will be painted with its default appearance; a) 'menulist' or 'menulist-button', b) 'none', and c) 'none'.Though they will have rendering results which web authors don't expect, I think users still can operate with A and B elements. C would have troubles that users can't know elements are clickable.
https://www.chromestatus.com/metrics/feature/timeline/popularity/2579 - search that are not really search. What is the worst case scenario here? Is it just that the cross button stops being available in a text field or is there more to it?The cross button in input[type=search] won't be affected. If a web page has style like "div.cancel { -webkit-appearance: searchfield-cancel-button; }", the element will have no cross button, and users might be unable to find the element.Actually, this counter value is too high due to a bug of the counting code. The counter unexpectedly contains usage with ::-webkit-clear-button pseudo elements, which is used in input[type=date/datetime-local/month/time/week] on non-Android Chrome and won't change behavior. The fixed counter is https://www.chromestatus.com/metrics/feature/timeline/popularity/2905, and the counter is available since Chrome 76.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHpF%2B42LpYOaa2_1Q%2BA6zN5pjw3Y7xy-3tX%3DdVbEfYMFA%40mail.gmail.com.
On Fri, Jul 12, 2019 at 5:02 AM TAMURA, Kent <tk...@chromium.org> wrote:On Fri, Jul 12, 2019 at 5:07 AM Daniel Bratell <bra...@opera.com> wrote:Hi tkent!This looks like a nice cleanup and for all but two the usage numbers are so low that there is no reason to worry, but there are two that are a bit higher.https://www.chromestatus.com/metrics/feature/timeline/popularity/2774 - for things that are not buttons but want to look like buttons. What is the worst case scenario here? What happens if this appearance disappears?I'd like to categorize this into three use cases:a) Drop-down box <select> with 'button' appearanceb) Hyper-link <a href="..."> with 'button' appearance; https://www.chromestatus.com/metrics/feature/timeline/popularity/1470c) Others; e.g. <div> with 'button' appearanceIn any case, an element will be painted with its default appearance; a) 'menulist' or 'menulist-button', b) 'none', and c) 'none'.Though they will have rendering results which web authors don't expect, I think users still can operate with A and B elements. C would have troubles that users can't know elements are clickable.C is indeed the scary case. Could we remove everything but C and look at usage at that point?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEim3bkFvboBYjzVTu34CVDdVQxiN1UCGjNTbHOfhYCWkg%40mail.gmail.com.
On Fri, Jul 12, 2019 at 2:33 PM Yoav Weiss <yo...@yoav.ws> wrote:On Fri, Jul 12, 2019 at 5:02 AM TAMURA, Kent <tk...@chromium.org> wrote:On Fri, Jul 12, 2019 at 5:07 AM Daniel Bratell <bra...@opera.com> wrote:Hi tkent!This looks like a nice cleanup and for all but two the usage numbers are so low that there is no reason to worry, but there are two that are a bit higher.https://www.chromestatus.com/metrics/feature/timeline/popularity/2774 - for things that are not buttons but want to look like buttons. What is the worst case scenario here? What happens if this appearance disappears?I'd like to categorize this into three use cases:a) Drop-down box <select> with 'button' appearanceb) Hyper-link <a href="..."> with 'button' appearance; https://www.chromestatus.com/metrics/feature/timeline/popularity/1470c) Others; e.g. <div> with 'button' appearanceIn any case, an element will be painted with its default appearance; a) 'menulist' or 'menulist-button', b) 'none', and c) 'none'.Though they will have rendering results which web authors don't expect, I think users still can operate with A and B elements. C would have troubles that users can't know elements are clickable.C is indeed the scary case. Could we remove everything but C and look at usage at that point?For now, we have a counter for A + C. https://www.chromestatus.com/metrics/feature/timeline/popularity/2775 0.005%. So C must be less than 0.005%.
If 0.005% still looks high, how about changing the plan like:M77: Show deprecation messages for all cases, and add a counter for C.After M77 stable promotion: Check the counter value, and make a decision about C.M79: Change the behavior with/without C.
On Fri, Jul 12, 2019 at 8:00 AM TAMURA, Kent <tk...@chromium.org> wrote:On Fri, Jul 12, 2019 at 2:33 PM Yoav Weiss <yo...@yoav.ws> wrote:On Fri, Jul 12, 2019 at 5:02 AM TAMURA, Kent <tk...@chromium.org> wrote:On Fri, Jul 12, 2019 at 5:07 AM Daniel Bratell <bra...@opera.com> wrote:Hi tkent!This looks like a nice cleanup and for all but two the usage numbers are so low that there is no reason to worry, but there are two that are a bit higher.https://www.chromestatus.com/metrics/feature/timeline/popularity/2774 - for things that are not buttons but want to look like buttons. What is the worst case scenario here? What happens if this appearance disappears?I'd like to categorize this into three use cases:a) Drop-down box <select> with 'button' appearanceb) Hyper-link <a href="..."> with 'button' appearance; https://www.chromestatus.com/metrics/feature/timeline/popularity/1470c) Others; e.g. <div> with 'button' appearanceIn any case, an element will be painted with its default appearance; a) 'menulist' or 'menulist-button', b) 'none', and c) 'none'.Though they will have rendering results which web authors don't expect, I think users still can operate with A and B elements. C would have troubles that users can't know elements are clickable.C is indeed the scary case. Could we remove everything but C and look at usage at that point?For now, we have a counter for A + C. https://www.chromestatus.com/metrics/feature/timeline/popularity/2775 0.005%. So C must be less than 0.005%.0.005% is lower than what I thought it would be initially.If 0.005% still looks high, how about changing the plan like:M77: Show deprecation messages for all cases, and add a counter for C.After M77 stable promotion: Check the counter value, and make a decision about C.M79: Change the behavior with/without C.That plan SG, but might be a bit too restrictive. Maybe we could go ahead with everything but C, while collecting data on C and making a separate decision about it for M79?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgmCvikML8Uf_t%2BV7o%3DxGjh1hLwfNuO4TJYrjOYniwayA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqFoqccrvDLso7g34BWKEqK2rHqb3Kj2dBDZHi5L%3D5-ybQ%40mail.gmail.com.