Jean-Yves Perrier
Jean-Yves Perrier
Yes, we need one implementation (not behind a flag) before merging a feature into MDN. We document browsers and not specs.
Oh yes, you are right. I think this error can't happen anymore. Nevertheless, I'm worried that the issue reporter said there are still links to this page from inside Firefox...
Can you remove from this PR the unrelated pages? Thank you!
This will fixes #19075
Also, for the example, it should be possible to adapt the live example found [there](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/inert).
Thanks! I think we should wait for an implementation before merging this. Implementation can get stalled. What about making this a draft PR meanwhile?
Can we wait before trying to solve this issue? @wbamberg will know what the best course of action is.
> Regarding: `files/en-us/web/api/bluetoothremotegattcharacteristic/writevalue/index.md` Looks like it can't have deprecated and experimental statuses at the same time. The browser-compat-data build fails with following error: > > ``` > Testing all features...
> The `math-depth` and `math-style` properties are defined in the MathML Core spec (https://w3c.github.io/mathml-core/#the-math-style-property), which doesn't appear in the webref CSS specs. Should it? It should, see w3c/webref#681 for how...
We have to pay attention to two things: - exceptions. For example, there is a page that speaks about curly braces, and this shouldn't be replaces - `for...of`, `for...in`, etc....