Daniel D. Beck

> Should we start with that date, and adjust the linter to throw an Error if the cut off date is not equal to the latest ranged value release date...

Also, if I'm wrong about this and BCD _is_ right, then I'm happy to take on the task of contributing fixes back to caniuse.

> So, this will move this feature from baseline high back to limited availability. I think that's correct based on: > > * https://bugs.webkit.org/show_bug.cgi?id=195884#c4 > > * https://medium.com/@brunn/autofocus-in-ios-safari-458215514a5f I think...

For background, mdn/browser-compat-data recently marked `HTMLElement.popover` as partially-implemented, due to popovers being undismissable in some circumstances in Safari on iOS. Apparently, this bug has been around since popover shipped in...

https://github.com/mdn/browser-compat-data/issues/25077 is resolved in BCD. Since web-features v2.21.0, [popover is shown as being newly available](https://github.com/web-platform-dx/web-features/blame/v2.21.0/features/popover.yml.dist). This appears now on webstatus.dev. I think this issue can be resolved. The complete history...

This one took a little more investigation than [popover](https://github.com/GoogleChrome/webstatus.dev/issues/739). The actual status is derived from some upstream browser compat data, specifically a note on Safari for iOS that marked it...

We had a conversation today about showing tentative banners. Here's a possible flowchart for deciding whether show/hide or caveat a banner:  [Source in the D2 playground](https://play.d2lang.com/?script=dFI9sqMwDO59Cg392wNQLMVus_VrmWFEUGJNHCljO2G4_Y4NBAfyqjjfn4T9hYg-1vCdfsCSJ2Mshu6ktzvGGv4qBYiWA9zxQq1YfBIgzDRcaWoK-a9g8U41DIw3lcGYK00dS3cmjA9PNfxLWVS4gaUVhJH6r0UUYDk0O_ch_KaeumhROhXqrjSt-Z4gcZA4UKFWvI7AUs6O2DtqjhmHKSd1jk6xhj_zYXbOkSFifAQKq2g16xOdMQOfz-RZLukWAWUCPecVcgKUAa3MYhg52qyxhINjoUXSbGmHDUf1YbvbnREqp2MF_SO2gs5tswOgJ6gsX2wF6mddM4cdRnDoHN840vDTnFaqRQH4RHbYs-M4VU3hPcSK1vBtdQTRVnoUIW8mCgs4A_lKNK8vgCGS53A16-EofdeZXG_4-g1bS8uCJyZtIboD982dKOzrXHiPxIdy5ogDnsT5m0U_k68CZv_yLxGvRhRVS3j5WMnzRq6jimd5wUn8Di_VSvp8fJO-kO0xRM3_AAAA__8%3D&)

An issue on web-features alerted me to one more asterisk-worthy case: [when there's a split between desktop and mobile browsers of the same brand](https://github.com/web-platform-dx/web-features/issues/1792). This new flow chart handles that...

Here's a revised flowchart, handling the discouraged case (new question in orange) ![rather long complicated flow chart; if the source linked below is unhelpful, please let me know and I'll...

One thing that this version of the chart doesn't cover is **a compat key in multiple features**, which is related to but not strictly dependent on the method used to...