Schalk Neethling

@maboa See here: https://github.com/mdn/interactive-examples/tree/master/__tests__

@ikarasz Could we break them up into separate test suites and run each suite separately in parallel? THinking out loudly, I have not actually looked at how possible this is.

@wbamberg Also, do you feel we should block merging https://github.com/mdn/interactive-examples/pull/440 until we solve this?

Dang, you are right this is trickier than I initially thought. > I wonder if it would be OK to just treat "not supported" and "bad syntax" as the same...

@chrisdavidmills Yeah, I was thinking of something like this myself. BCD came to mind but, not sure whether that is in a state that we can entirely rely on yet....

## Acceptance Criteria Documentation and proposal on handling scenarios where either a single property, or an entire feature is not supported. The proposal should include a visual prototype and how...

@wbamberg I was thinking over this some more, what if we use an approach such as in this POC. https://codepen.io/schalkneethling/pen/GBxoQM Let me know your thoughts?

> Yes, it is worth fixing (and not too difficult) @schalkneethling Do you think you can provide the list of 404 pages with _Core_JavaScript_1.5_Guide_ in their slug over the last...

@mdn/core-dev I have also run into this with `/community` if used without a `locale`. https://developer.mozilla.org/community is a 404 but https://developer.mozilla.org/en-US/community is fine

> @schalkneethling , this continues to confuse people: #1826. Do you think there's any likelihood that we could implement something that completely hides the editor if a property isn't supported?...