If no JavaScript is available Gutenberg is only showing an admin notice that Javascript is required instead of the actual content

[rpkoller]

I've already pointed out the details in #2719 over a year ago that the editor should provide a progressive enhancement experience. Meaning never ever should the content be inaccessible by the user. There are many scenarios that Javascript might not be available https://kryogenix.org/code/browser/everyonehasjs.html not only if the functionality is actually switched off in the browser. The issue got agreed on by several stakeholders over the course of several months but in the end got hi-jacked by the half baked makeshift admin notices solution which isnt fixing the initial ticket at all. @mkaz recommended that i shall open a new ticket again.

[karmatosed]

I am removing the 'User Experience (UX)' label as part of a label cleanup. It's not being used anymore consistently so let's try and keep to 'needs design' and 'needs design feedback'. If we find a need for another label we can consider it but having those 2 should cover this.

[sarahmonster]

The design team discussed this during a triage session in Slack today (Note: You may need a Slack account to log in.)

Overall consensus was that this would be great from a design perspective, but there may be architectural hurdles to accomplishing this well. We'd love some feedback from a technical perspective here.

[rpkoller]

@sarahmonster the technical feedback was already given back in september 2017 by @ellatrix in the original issue: #2719 (comment)