Skip to content

Conversation

@ellatrix
Copy link
Member

@ellatrix ellatrix commented Mar 14, 2019

Description

Attempt to expand phrasing content schema. This also prevents stripping of some content when transforming legacy content to blocks.
Partial fix for #17879.

How has this been tested?

Screenshots

Types of changes

Checklist:

  • My code is tested.
  • My code follows the WordPress code style.
  • My code follows the accessibility standards.
  • My code has proper inline documentation.
  • I've included developer documentation if appropriate.

Copy link
Member

@jorgefilipecosta jorgefilipecosta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I wrote the comment that was supposed to be on #14430 here by mistake.

@ellatrix ellatrix added the [Status] In Progress Tracking issues with work in progress label Apr 24, 2019
@ellatrix ellatrix force-pushed the try/phrasing-content-schema branch from a074161 to a9ed24a Compare December 10, 2019 11:36
@ellatrix ellatrix marked this pull request as ready for review December 10, 2019 11:44
@ellatrix ellatrix force-pushed the try/phrasing-content-schema branch from a9ed24a to a7c0520 Compare December 10, 2019 12:21
@ellatrix ellatrix added [Feature] Paste [Type] Enhancement A suggestion for improvement. and removed [Status] In Progress Tracking issues with work in progress labels Dec 10, 2019
@ellatrix ellatrix merged commit 78760fa into master Dec 10, 2019
@ellatrix ellatrix deleted the try/phrasing-content-schema branch December 10, 2019 13:09
@ellatrix ellatrix changed the title Raw handling: update phrasing content schema Raw handling: expand phrasing content schema Dec 10, 2019
@youknowriad youknowriad added this to the Gutenberg 7.2 milestone Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Feature] Paste [Type] Enhancement A suggestion for improvement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants