sideshowbarker
sideshowbarker
I marked this as Draft just so that we don’t end up merging it prematurely before we’ve had a chance to get the potential review requested in https://github.com/mdn/content/pull/21872#issuecomment-1293379804
I believe this happens because in https://github.com/w3c/browser-specs/blob/main/index.json, `https://svgwg.org/svg2-draft/` is listed at the `nightlyUrl` for both the `SVG11` spec and for the `SVG2` spec — and I guess our client code...
This has merge conflicts
Miguel, thanks much, and congrats on landing your first docs change here — welcome aboard 🎉
@qibing147147 > Remove mozItemCount, mozClearDataAt, mozGetDataAt and mozSetDataAt completely? ut if someone still wants to use these apis on the old browser,they may not be able to see these apis...
> Is that OK, you think? I think @evilpie should be the one to decide what’s OK here — since he’s the one who raised the issue this PR is...
> I'd like to ask u a question. > > Why is the Markdownlint executed incorrectly? I don’t know. We’ve been having a variety of `git`-related failures with the Markdown...
@qibing147147, thanks much, and congrats on landing your first docs change here — welcome aboard 🎉
Yeah that “The "Unicode Problem"” section rightly should not be buried in a glossary entry. But it was added a very long time ago, and is now linked to from...
Thanks for catching this and reporting it — I’ve opened #22123 with a fix. After that fix is merged, this issue will automatically be marked as resolved, and closed.