Peter Bengtsson

Actually, how is this different from https://github.com/mdn/kuma/issues/6600 ?

I created this: https://developer.allizom.org/en-US/docs/Web/SVG/Element/feTurbulence

CC @wbamberg @hamishwillee I just copied, verbatim, [what Hamish suggested here](https://github.com/mdn/yari/issues/3931#issuecomment-853440653).

Actually, mentioning German is funny because I realize a "bug" in this. The de pages are not maintained. You can't file an issue, because there is no team of reviewers...

> Are there redirects in place for any of our 'deprecated locales' (see what I did there) @peterbe ? Yeah, that's already in place. E.g. https://developer.mozilla.org/sv-SE/docs/Web/CSS But let's not spend...

> If JS is not enabled it will affect Yari as well and it will serve the static "unhydrated" HTML in which case the IEx will be hidden anyway). Nitpicking...

I'm so confused. Why is https://interactive-examples.mdn.mozilla.net/pages/css/offset-anchor.html not working in Chrome? Suppose `offset-anchor` doesn't work in Chrome ([even though it should](https://developer.mozilla.org/en-US/docs/Web/CSS/offset-anchor#browser_compatibility)) If there's something in the bob JS that is broken,...

Oh I see. ```js if ( mceUtils.isPropertySupported(exampleChoiceList.dataset) && !document.all ) { enableLiveEditor(); ... } ``` And `enableLiveEditor()` is what removes the default hardcoded `hidden` class names. (from `editable-css.js`). I think...

Which brings me to my second question, why is `mceUtils.isPropertySupported(exampleChoiceList.dataset)` becoming false on that page when the BCD table says `offset-anchor` should work in Chrome (since version 79)??

What if you do: ```diff -if ( - mceUtils.isPropertySupported(exampleChoiceList.dataset) && - !document.all - ) { + if (1) { enableLiveEditor(); ``` does the example start to work in Chrome? If...