Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #38061, comment 22


Ignore:
Timestamp:
11/21/2017 07:35:48 AM (7 years ago)
Author:
mark-k
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #38061, comment 22

    initial v1  
    55Back in the prehistoric days when editing was done in a textbox it was a mix of raw html to be displayed on the front end and text which was automatically translated into html. Not very elegant but you did not had to be a rocket scientist to get it.
    66
    7 Then came shortcodes, oembeds, massive use of the_content filter in general and now gutenberg wants to add raw data into it. This is a mess that I doubt anyone can describe in less than 10 minutes to anyone else no matter what is his technical understanding level. Too many things here are too much of wordpress internals.
     7Then came shortcodes, oembeds, massive use of the_content filter in general and now gutenberg wants to add raw data into it (and there is also the kses which might cause that what is saved is not what is displayed there) . This is a mess that I doubt anyone can describe in less than 10 minutes to anyone else no matter what is his technical understanding level. Too many things here are too much of wordpress internals.
    88
    99The only reasonable name for that tab is probably "raw" which will probably cause everyone with 100 IQ to rightfully avoid using it, which leads to the question why should it exist in the first place. If tinymce now generates a good enough HTML, why can't the "html" editing be relegated into a plugin?
    10 The other option is to actually define in positive word what that tab is, and then the name will suggest itself.
     10The other option is to actually define in positive way what that tab is, and then the name will suggest itself.