Making WordPress.org

Changes between Version 15 and Version 33 of Ticket #6608


Ignore:
Timestamp:
12/14/2022 11:02:37 AM (15 months ago)
Author:
dd32
Comment:

Ensure that fixes we've applied for <li> in the past continue to work.

Our fix still prevents nested lists from the Editor working, but that's OK for now.

Ensure that blocks copy-pasted from other Block Editor Instances pastes correctly into the Support forum editor.

This mostly works, unless you copy a block that we don't support, instead of getting an error.. nothing happens. This can be duplicated by copying a HTML block from wordpress.org/gutenberg.

Evaluate if an option to disable the Block editor on a per-user profile option is practical.

This appears to be an option now, however, is something we'd like to avoid if possible.

Evaluate additional blocks to be enabled, or created

Some upstream work has been done to create a custom Paragraph block which resolves some/most of our paste issues. Blocks for Site Health and other related things would be beneficial, but isn't needed for an MVP here.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6608 – Description

    v15 v33  
    1313🔲 Evaluate if an option to disable the Block editor on a per-user profile option is practical. This might be an option, we still need to decide if we wish to support that though. [https://github.com/Automattic/blocks-everywhere/issues/55 upstream issue]
    1414🔲 Evaluate additional blocks to be enabled, or created, for the forums. This may include a "Pasted content" block as below, or other blocks such as pre-defined replies for members of the support team and/or plugin/theme support reps.
    15 🔲 Evaluate Upstream issues in [https://github.com/Automattic/blocks-everywhere/issues Automattic/blocks-everywhere]. ''(please report any major issues in the plugin upstream, if it doesn't seem WordPress.org-specific)''
    16 
    17 '''Upstream Blockers'''
    18 🔲 Ensure that pasting logs works. The existing "wrap it in code tags" doesn't work well, and when pasting into the Block Editor it will split it into many blocks instead. This behaviour makes sense for most uses of the Block Editor, but creates a worse UX for the forums, especially when it comes to attempting to combine the logs into a singular block. [https://github.com/Automattic/blocks-everywhere/issues/54 Upstream Issue]
     15✅ Evaluate Upstream issues in [https://github.com/Automattic/blocks-everywhere/issues Automattic/blocks-everywhere]. ''(please report any major issues in the plugin upstream, if it doesn't seem WordPress.org-specific)''
     16✅ Ensure that pasting logs works. The existing "wrap it in code tags" doesn't work well, and when pasting into the Block Editor it will split it into many blocks instead. This behaviour makes sense for most uses of the Block Editor, but creates a worse UX for the forums, especially when it comes to attempting to combine the logs into a singular block. [https://github.com/Automattic/blocks-everywhere/issues/54 Upstream Issue]
    1917
    2018''Additional items to be edited in here as discovered, please comment below. Bug Gardeners: Please edit my ticket too! ''