What problem does this address?
In DataViews there are two issues.
- Edit can appear twice.
- A single menu item just with 'edit' can be seen on for example Templates. Where on pages this might be a pancil icon and also in menu.
What is your proposed solution?
Overall, I would suggest not using hidden option menus. However, that patterns iteration is a longer discussion. I would like to focus on a fix that can clean up this situation. Then looking at ways to expose as much as possible on interaction over use any hidden menus would be the way forward.
Option one: Remove the pencil icon and only have edit in the menu.
This is less than ideal as the primary action is probably 'edit,' which is why it was exposed in the first place.
The reason to do this might be that the pencil icon is less accessible, but I would love feedback on this. Having hidden features might be less desirable in an options menu.
Evidence to maybe do this is that the Post screen hasn't got an exposed primary action:
Option two: Remove edit from the menu
As it is exposed as a primary feature anyway, this means that this interaction would be true:
- Any primary action is visible outside the menu and removed as text in menu.
- The options menu with just 'edit' would be removed, and the pencil icon would be added.
This could also apply to other cases. In the case of the Post screen, this could even make rename work by clicking inside the field later. That feels outside the scope of this ticket but is a natural behaviour expected by fields. I think 'view' is the primary. This is one of the issues with these hidden menus and only exposing the primary.
What problem does this address?
In DataViews there are two issues.
What is your proposed solution?
Overall, I would suggest not using hidden option menus. However, that patterns iteration is a longer discussion. I would like to focus on a fix that can clean up this situation. Then looking at ways to expose as much as possible on interaction over use any hidden menus would be the way forward.
Option one: Remove the pencil icon and only have edit in the menu.
This is less than ideal as the primary action is probably 'edit,' which is why it was exposed in the first place.
The reason to do this might be that the pencil icon is less accessible, but I would love feedback on this. Having hidden features might be less desirable in an options menu.
Evidence to maybe do this is that the Post screen hasn't got an exposed primary action:
Option two: Remove edit from the menu
As it is exposed as a primary feature anyway, this means that this interaction would be true:
This could also apply to other cases. In the case of the Post screen, this could even make rename work by clicking inside the field later. That feels outside the scope of this ticket but is a natural behaviour expected by fields. I think 'view' is the primary. This is one of the issues with these hidden menus and only exposing the primary.