Opened 5 years ago
Last modified 4 years ago
#48279 new enhancement
Avoid block markup in starter content and default pages
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 5.0 |
| Component: | Editor | Keywords: | |
| Focuses: | administration | Cc: |
Description
In #45151 the Hello World, Sample Page and Privacy Policy content were updated to supply block markup for the editor. The Privacy Policy was the only one that took into account the classic editor and avoided providing the markup in that case as it was also used on the guide which isn't an editor page.
In #48130 the starter content is being updated to account for the block editor by adding the necessary markup.
It would be nice for users of the classic editor to suppress that markup when they're not using the block editor similar to what was done for the Privacy Policy content.
Change History (2)
#2
in reply to:
↑ description
@
4 years ago
Replying to garrett-eclipse:
It would be nice for users of the classic editor to suppress that markup when they're not using the block editor similar to what was done for the Privacy Policy content.
Could you elaborate on this? What does the Privacy Policy page do?
I'm actually thinking that since the starter content can be filtered, core should cater towards the block approach, and any plugin that enabled the classic editor could filter out the block aspect of it if they so desire?
With block-notations being HTML comments, they won't cause any problems with the content it self in a classic editor scenario, and the byte-count of a paragraph is negligible in the big picture to be a concern as well.