Opened 8 years ago
Last modified 13 months ago
#12685 new enhancement
Add action menu for creating, deleting and modifying resources or parts thereof
Reported by: | Christian Boos | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | general | Version: | 1.3dev |
Severity: | normal | Keywords: | layout menu |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
With this menu, it would be easier to perform actions on resources (wiki page, ticket #10948, ticket comment #12671).
The idea would be to remove from the contextual navigation the link what's not a navigation to another resource (e.g. wiki history is rather an action on the resource itself, show me the page's history), and to gather the bottom of the page buttons (Edit, Delete, Rename) into a contextual menu at the top of the resource, a bit like what we have now for the ticket comment.
Copied from 12671#comment:2:
Replying to Jun Omae:
… the buttons are shown only when cursor is hovered in property changes box. As the results, it is difficult to click the buttons.
But also the whole <h3> line as well, in particular the comment:n
part which is just above the buttons. But I think you're right anyway, it's not as obvious as it should be.
If you remember my idea presented recently on trac-dev about a "page menu" (gmessage:trac-dev:eVU0q8Tatgo/pokz_FIyEQAJ), I think it could be transposed here as well: we would have a permanent menu reminder character/icon (▤, ≣), which would show the list of actions for the comment when hovered / clicked.
Something like:
comment:n Modified by Author
Attachments (0)
Change History (10)
comment:1 by , 8 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:2 by , 8 years ago
follow-up: 7 comment:4 by , 8 years ago
[OT] By the way, despite the fixing above, when I add some comment and click "Preview", in Chrome (57.0.2987.110, Windows) I get an "ERR_BLOCKED_BY_XSS_AUDITOR" error. Sending the page to the validator doesn't show anything obvious… Does anyone else experience the same thing?
comment:5 by , 8 years ago
Same with 57.0.2987.98 on OSX, and then still after upgrading to 57.0.2987.110.
comment:6 by , 7 years ago
It's not surprising that relying on JavaScript to show buttons causes issues in some browsers.
It also makes https://trac.torproject.org impossible to use with JavaScript off (Tor Browser high security mode).
comment:7 by , 7 years ago
Replying to Christian Boos:
[OT] By the way, despite the fixing above, when I add some comment and click "Preview", in Chrome (57.0.2987.110, Windows) I get an "ERR_BLOCKED_BY_XSS_AUDITOR" error. Sending the page to the validator doesn't show anything obvious… Does anyone else experience the same thing?
Also reported in #12926, which has a proposed fix.
comment:9 by , 5 years ago
Milestone: | next-dev-1.5.x → next-major-releases |
---|
comment:10 by , 5 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
Take ticket:12639#comment:23 and #10948 into account.