- Issue created by @wim leers
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Signaling this needs a CKEditor 5 feature.
Follow-up for 📌 `StringSemanticsConstraint::MARKUP`: agree how SDC prop JSON schema can convey it should be markup, and Needs review .
There's 2 challenges to "inline HTML props". Those props can be recognized by the following prop schema:
type: string
contentMediaType: text/html
x-formatting-context: inline
This corresponds to an "inline" text format (xb_html_inline) that intentionally does not allow <br> per @lauriii at
#3467959-42: SDC and code component props should be able to receive HTML, editable in CKEditor 5 →
.
Challenges:
<p>, <ul> and other block-level elements). So any such SDC props are unlikely to be able to get populated by structured content.<br> is supported at minimum, but that is intentionally excluded from the xb_html_inline text format.And ironically, #2 means #1 is literally impossible anyway in the near future!
@lauriii suggested a reasonable work-around: XB should match a
Drupal \Drupal\Core\Field\Plugin\Field\FieldType\StringItemfield against atype: string; x-formatting-context: inlineSDC prop.
— #3467959-38: SDC and code component props should be able to receive HTML, editable in CKEditor 5 →
… but doing this would:
type: string and type: string, contentMediaType: text/html, x-formatting-context: inline would result in exactly the same matches! So then why even ever use the latter?!
Conclusion: proposed resolution still TBD.
TBD
Postponed
0.0
Shape matching
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
Signaling this needs a CKEditor 5 feature.