[wp-trac] [WordPress Trac] #59310: Parse blocks being applied unnecessarily

[WordPress Trac]

#59310: Parse blocks being applied unnecessarily
--------------------------+------------------------------
 Reporter:  spacedmonkey  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.3.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  performance
--------------------------+------------------------------

Comment (by aduth):

 Yes, the referenced patch was related to a security vulnerability, so I’d
 exercise caution with any revisions. That said, there were additional
 tests in the private security test suite beyond what’s included in the
 public commit, which may provide some assurances to avoid a regression.

 As far as fields where block content isn’t expected or supported, I don’t
 specifically recall if those were susceptible in the same way, so it might
 be possible to exclude them specifically for some gains.

 There may also be some options to optimize such that it’s only applied at
 save-time, but it’d need to be done in a way that handles legacy content.

 I’d suggest collaborating with someone on the security team to navigate
 any potential regressions, as well as to help run the security test suite
 against any proposed patches.

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