Remove links to internal pages with broken tools

[estelle]

Remove links to tools that aren't currently working

[github-actions]

Preview URLs

• /en-US/docs/Web/CSS/CSS_backgrounds_and_borders
• /en-US/docs/Web/CSS/box-shadow

Flaws (3)

Note! 1 document with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/CSS/CSS_backgrounds_and_borders
Title: CSS backgrounds and borders
Flaw count: 3

• macros:
  • /en-US/docs/Web/CSS/background-position-inline does not exist
  • /en-US/docs/Web/CSS/background-position-block does not exist
  • /en-US/docs/Web/CSS/line-type does not exist

[bsmth]

What's the motivation to remove links to these?

[hamishwillee]

What's the motivation to remove links to these?

As @estelle says "links to tools that aren't currently working"

The with this is that it is hard to remember that you need to restore the links when the tools are working, and I wonder why they aren't working.

So personally I'd lean towards leaving the links but creating a clear warning on the linked page about the status of the tools.

[chrisdavidmills]

@estelle What is not working about these tools? I just tested them in Fx and Chrome, and they seemed to be working for me.

[wbamberg]

It depends what you mean by "not working". The layout/design of the tools has been broken ever since the MDN redesign in 2022, and there is a bug on file here: mdn/yari#5392 for that.

That issue links to several other issues that have been filed on mdn/content, which are basically duplicates.

Functionally the tools seem to work, although they've not had any updates for several years so don't support any syntax added since then. There is mdn/css-examples#157, which claims to be a functional issue but I think probably isn't (and if it isn't, should be closed as a duplicate of mdn/yari#5392).

However it's hard to argue that they are not a bad user experience for a professional site, to put things politely. Whether that's enough to stop linking to them, I don't know.