WordPress.org

Making WordPress.org

Opened 2 years ago

Last modified 7 months ago

#3992 new enhancement

Gutenberg Theme: Add old-browser fallback

Reported by: dd32 Owned by:
Milestone: Priority: low
Component: General Keywords:
Cc:

Description

Currently the Gutenberg theme in old browsers is broken as it requires more modern browsers.

One particular error in IE9 is `'Blob' is undefined' which makes sense as that's not available until IE10.

Additionally, we should consider some 'richEditing' fallback as shown by [7970] and https://github.com/WordPress/gutenberg/issues/12772

I think we might be able to get away with a large centered block which suggests the browser is too out of date, linking off to https://browsehappy.com/ and maybe mentioning Gutenbergs browser requirements.

For reference, I'm attaching what it currently looks like in IE9.

Attachments (4)

Gutenberg_VirtualBox_IE9.png (33.3 KB) - added by dd32 2 years ago.
Screen Shot 2020-03-25 at 2.26.58 PM.png (233.3 KB) - added by dufresnesteven 8 months ago.
What about something like this? The colors are from Gutenberg's Notice component.
3992.diff (2.6 KB) - added by dufresnesteven 7 months ago.
What about something like this? A css hack could also work but i prefer not to have anything in the DOM for indexing purposes.
Screen Shot 2020-04-17 at 3.08.49 PM.png (227.5 KB) - added by dufresnesteven 7 months ago.
Previous diff visual outcome for ie < 11

Download all attachments as: .zip

Change History (8)

#1 @dufresnesteven
8 months ago

I concur.

According to the official documentation https://make.wordpress.org/core/handbook/best-practices/browser-support/, Gutenberg supports IE 11+.

@dufresnesteven
8 months ago

What about something like this? The colors are from Gutenberg's Notice component.

#2 follow-up: @dd32
8 months ago

What about something like this? The colors are from Gutenberg's Notice component.

Something like that would be okay, but realistically unsupported browsers are currently going to be a WSOD as all JS execution will be failing. I guess that probably means we'd have to have it as the default HTML of the page that the editor then replaces?

#3 in reply to: ↑ 2 @dufresnesteven
8 months ago

Replying to dd32:

What about something like this? The colors are from Gutenberg's Notice component.

Something like that would be okay, but realistically unsupported browsers are currently going to be a WSOD as all JS execution will be failing. I guess that probably means we'd have to have it as the default HTML of the page that the editor then replaces?

Yeah, you're 100% correct. We'd have to put it above the Gutenberg controls.

@dufresnesteven
7 months ago

What about something like this? A css hack could also work but i prefer not to have anything in the DOM for indexing purposes.

@dufresnesteven
7 months ago

Previous diff visual outcome for ie < 11

#4 @dufresnesteven
7 months ago

Noting, that diff is experimental.

The copy should be improved.

I just want to validate the approach.

:)

Note: See TracTickets for help on using tickets.