close
Skip to content

Unsupported Block: Improve messaging to convey the block can be edited using UBE #62050

@fluiddot

Description

@fluiddot

Description

When a block is not supported in the native mobile version, it's rendered as unsupported but it can still be edited using the Unsupported Block Editor (UBE). However, the message displayed in the block ("Unsupported") doesn't really convey that if you tap two times on it, an alternative edit option will be presented.

Step-by-step reproduction instructions

  1. In the browser, create/open a post and add a block that is not supported on native mobile (e.g. Table block).
  2. Save the post.
  3. Open the post in the app.
  4. Observe the block is rendered as unsupported.
  5. Observe the message doesn't convey that the block can be edited using UBE.

Expected behaviour

The unsupported block's message conveys that the block can be edited using UBE.

Actual behaviour

The unsupported block's message doesn't convey that the block can be edited using UBE.

Screenshots or screen recording (optional)

Image

WordPress information

  • WordPress version: N/A
  • Gutenberg version: N/A
  • Are all plugins except Gutenberg deactivated? N/A
  • Are you using a default theme (e.g. Twenty Twenty-One)? N/A

Device information

  • Device: N/A
  • Operating system: Android and iOS
  • WordPress app version: 24.8.0.4

Metadata

Metadata

Assignees

Labels

Mobile App - i.e. Android or iOSNative mobile impl of the block editor. (Note: used in scripts, ping mobile folks to change)[Status] In ProgressTracking issues with work in progress[Type] EnhancementA suggestion for improvement.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions