WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #37974, comment 112


Ignore:
Timestamp:
10/11/2016 09:52:22 PM (3 years ago)
Author:
karmatosed
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #37974, comment 112

    initial v1  
    33> I can make this change, but I'm not really a fan of making destructive operations so easily accessible without a confirmation, especially considering how close to other controls it is. They would also be the most visible controls on the screen even though they're not the primary action.
    44
    5 This change is important as otherwise you are hiding functionality. I do not feel that making it manage sections solves this, unfortunately. I did a little unorganised testing with another user and found it to be an issue to find delete. I also felt this in my own design process. Can we please have as the mock for this instance? I am very against hiding functionality and this is something that does cause user friction.
     5This change is important as otherwise you are hiding functionality. I do not feel that making it manage sections solves this, unfortunately. I did a little unorganised testing with another user and found it to be an issue to find delete. I also felt this in my own design process. With menus you have also the ability to click in and remove. As we don't, we loose the instant interactions without the panel. I'm also not keen we add a click in just for this case.
     6
     7Can we please have as the mock for this instance? I am very against hiding functionality and this is something that does cause user friction.
    68
    79> tested this a bit more and it looks the front page does need to be the first section for the query and template loading to work correctly. Trying to make it sortable might open a big can of worms.