[wp-trac] [WordPress Trac] #60283: HTML API: Support all HTML tags in standard

[WordPress Trac]

#60283: HTML API: Support all HTML tags in standard
--------------------------------------+----------------------
 Reporter:  jonsurrell                |       Owner:  dmsnell
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.5
Component:  HTML API                  |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+----------------------

Comment (by dmsnell):

 Thanks for sharing your thoughts, @afercia. I don't think there's any
 comparison to Github here, or at least none was intended on my part; this
 is solely about Trac.

 There are a few things to note:
  - None of the HTML tag support patches have been done under a single Trac
 ticket. Some are individually not that complicated, but some are mini-
 projects on their own.
  - We'll likely be having lingering support patches for some amount of
 time.
  - This Trac ticket was not opened for the purposes I think you are
 describing; more or less it was accidentally created with a title that
 sounds like what you're suggesting.
  - As written, this ticket even excludes large portions of the HTML5
 specification from its scope, making it non-comprehensive even for the
 title'd purpose.

 So, as I responded to your first prompting, I think it would make sense,
 if we're requiring people not to split work into smaller pieces, to reuse
 #58517 since that seems to be more like what you are talking about
 requiring. I would appreciate your thoughts on that point; I'd like to
 imagine that this Trac ticket never existed, but it was created, and here
 we are.

 Also I'd like some thoughts from folks if there's strong feelings here or
 if it'd be fine to stay the course on the HTML API developments taking
 place in separate tickets. It can be hard to anticipate beforehand how
 complicated some section of the HTML5 specification will be to implement,
 and the discussion on this ticket, holding only a handful of relatively
 easy parts to implement, is already difficult for me personally to follow;
 there's too much noise and scrolling. Additionally, we inevitably get to
 things like the `PLAINTEXT` PR, which doesn't really belong here because
 as we got into it we realized that it's part of the Tag Processor's work
 and not part of the HTML Processor, so any merging of the work between the
 two is pushing the inherent relation that's there.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60283#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform