WordPress.org

Make WordPress Core

Changes between Version 3 and Version 4 of Ticket #42578, comment 24


Ignore:
Timestamp:
01/08/2018 06:28:27 AM (2 years ago)
Author:
jeremyescott
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #42578, comment 24

    v3 v4  
    33I can think of many cases where I wouldn't have been against a revert, like during development, during beta testing, even a week after release. '''But its been 8 weeks.''' For every stubborn theme dev who hasn't fixed their theme by now, there are many who have. Because its an easy fix. Either change a <p> to a <div> or change the escape from esc_html to wp_kses or something like it. But now you're gonna punish all the people who made that fix because some people didn't want to.
    44
    5 Its foolish to try and measure those who have fixed it against those who haven't and somehow decide who loses. But I will say, the businesses that make up the economy behind have already fixed it. The premium theme devs have already fixed it. They were fixing it on day 1, or even finding it during beta. They shouldn't get preferential treatment, but you know who should? Our end-users, the publishers.
     5Its foolish to try and measure those who have fixed it against those who haven't and somehow decide who loses. But I will say, the businesses that make up the ecosystem around WP have already fixed it. The premium theme devs have already fixed it. They were fixing it on day 1, or even finding it during beta. They shouldn't get preferential treatment, but you know who should? Our end-users, the publishers.
    66
    77The reason a lot of people may not have reported it as a bug during is simply that it fits the mission of WordPress: to make publishing easier. That line break... its important to unskilled publisher who is wondering why they can't make a paragraph in their bio. That line break matters. And you gave it to them. Now you want to take it away.