Filter policy help blocks away from the_content

[Clorith]

When creating a privacy policy page, we inject little help blocks that are read-only thanks to contenteditable="false". I like this, it means we have in-content help while writing, but since they're not regularly editable text fields it may not be obvious that you can remove these, or that you should remove them.

Could we perhaps introduce a filter for the_content that runs and removes these before the page is output?

[swissspidy]

I haven't looked at the code, but would it be possible to not save these help blocks in the first place? Makes more sense to me.

[Clorith]

Not saving them means you'd have to write everything in one sitting, as you would then lose them when you return. I can see this going both ways though.

[Clorith]

#43971 was marked as a duplicate.

[azaozz]

Yeah, was thinking about this too. If we keep the tutorial "blocks" (with contenteditable="false") in post_content (which is currently not the case), we may need to make sure they are kept on saving a draft and deleted on publishing.

Ideally the users will delete them before publishing, but we can "make sure" and have a filter that removes them too. Don't think we will need a "display filter", we can remove the tutorials on publishing and updating a published post.

[azaozz]

Fixed in [43203].

[desrosj]

Moving to the new Privacy component.