Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #19393, comment 64


Ignore:
Timestamp:
12/17/2013 02:40:21 PM (10 years ago)
Author:
bradt
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19393, comment 64

    initial v1  
    11Sorry @markoheijnen, but I'm not making the assumption you're accusing me of. Maybe you've misunderstood? I thought I'd given a very clear, very specific example where the ability to adjust the default crop position would have solved a painful real-world problem that has afflicted myself and I ''assume'' the majority of people cc'ed on this ticket.
    22
    3 It seems that whenever this patch gets to someone with the power to push it forward, they insist that the scope must be expanded to include a complete revamp of the image editor. This patch is very focused on default crop position so I don't understand why the scope must be expanded. I feel like I'm trying to get bill through congress here. There must be an unknown unknown that I'm missing. Perhaps someone can enlighten me?
     3It seems that whenever this patch gets to someone with the power to push it forward, they insist that the scope must be expanded to include a complete revamp of the image editor. This patch is very focused on default crop position so I don't understand why the scope must be expanded. I feel like I'm trying to get a bill through congress here. There must be an unknown unknown that I'm missing. Perhaps someone can enlighten me?
    44
    55I'd update this patch today if I was told the scope doesn't need to be expanded for it to be rolled into core.