Edgewall Software

Ticket #2036 (new defect)

Opened 3 years ago

Last modified 3 years ago

Inconsistent sub-menu on Browse Source comparing with View Tickets

Reported by: pkou at ua.fm Owned by: jonas
Priority: low Milestone: 1.0
Component: general Version: 0.9b1
Severity: minor Keywords:
Cc:

Description

Menu View Tickets contains two sub-items:

  • Available Reports
  • Custom Query

An item are not clickable when active.

In opposite, Browse Source contains one sub-item that changes its value depending on the active selection:

  • Revision Log
  • View Latest Revision

This needs to be unified in either way.

Attachments

Change History

Changed 3 years ago by cboos

If this needs unification, I would propose to modify the View Tickets to match Browse Source: only active links should be shown.

In the View Tickets, there's no point to show the inactive link, as this is redundant with the page title.

See also TracProject/UiGuidelines.

Changed 3 years ago by Manuzhai

I think it's good to show the inactive link. That way, links are always in the same place, allowing for effective muscle memory clicking.

Changed 3 years ago by cmlenz

  • milestone changed from 0.9 to 1.0

I agree with Manuzhai that showing the inactive link is good. It indicates where you currently are, as opposed to showing only where you can go.

The navigation links in the browser are not exactly the same story, however. View Latest Revision would need to be renamed, at least, because it would not make sense to show that label as inactive link when looking at an older revision.

Anyway, this can wait until after 0.9 IMO.

(And also IMO, the whole subnavigation story needs to be completely redesigned... it's a mess).

Add/Change #2036 (Inconsistent sub-menu on Browse Source comparing with View Tickets)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.