[wp-trac] [WordPress Trac] #58406: Post/Page Content Renders Empty

[WordPress Trac]

#58406: Post/Page Content Renders Empty
--------------------------+------------------------------
 Reporter:  svgator       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Formatting    |     Version:  6.2.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by cexopan):

 Replying to [comment:2 petitphp]:
 > IMHO this is more an issue with the content than with WordPress. Images
 should be inserted using a `<img>` tag and not inline because it creates
 really heavy content that take more time to download and are harder to
 parse for browsers.

 I disagree. For two reasons:
 1. It is not relevant that it was so much base64 data. It would fail with
 1M dots or 0s or 100,000 empty divs or whatever. Although 1M chars is
 quite a bit and certainly not your typical amount of HTML content it is
 actually possible without exceptional circumstances: I ran into the same
 problem with a gallery of 200 images served by Meow Gallery/Lightbox
 shortcode. In this case there is no base64 data, just pure HTML with some
 really big attributes.
 2. Moving on to PHP8 not dealing with an official return type ("false on
 failure") of preg_split() is asking for trouble. In PHP8 this results in a
 fatal TypeError in count().

 I hope you reconsider your assessment

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