Opened 13 years ago
Closed 11 years ago
#9210 closed defect (fixed)
/tags page should not have a contextual navigation link 'Cloud'
Reported by: | Ryan J Ollos | Owned by: | Steffen Hoffmann |
---|---|---|---|
Priority: | normal | Component: | TagsPlugin |
Severity: | normal | Keywords: | navigation |
Cc: | Steffen Hoffmann | Trac Release: | 0.11 |
Description
The /tags
page has a contextual navigation link Cloud. However, this link just points to /tags
, therefore it offers no functionality when on the /tags
page ... unless I am missing something?
It seems like the contextual navigation link should not be displayed when the /tags
page is displayed. I also question it's value when after a tags query has been submitted. It allows navigating back to the /tags
page, but one can also just click on the Tags entry on the mainnav.
Unless I'm missing something, it seems like the Cloud contextual nav entry is just cluttering up the contextual navigation.
Attachments (4)
Change History (18)
comment:1 follow-up: 2 Changed 13 years ago by
Keywords: | navigation added |
---|
comment:2 Changed 13 years ago by
Replying to hasienda:
While initially I'd agree, clutter=defect is a bit harsh ...
Agreed ... though it seemed a contradiction to call it an enhancement, even though that is probably how it is best described - enhance by removing clutter ;)
A bit far-fetched for such a small link - anyway: Should we detect tags.href<>"/tags" and hide/unhide that ctxtnav link accordingly?
Yeah, that was one thought that I had, and would seem to handle the mainnav
configuration case you mentioned. I think I could handle providing that patch ... I did a similar patch for the Trac core a while back.
comment:4 Changed 13 years ago by
Changed 13 years ago by
Attachment: | BackToQuery.png added |
---|
Changed 13 years ago by
Attachment: | BackToTicket.png added |
---|
Changed 13 years ago by
Attachment: | th9210-r10738-0.11.7-1.patch added |
---|
comment:5 follow-up: 11 Changed 13 years ago by
Owner: | changed from Ryan J Ollos to Steffen Hoffmann |
---|---|
Status: | new → assigned |
Simple but good idea, like it too. Let me sleep about it, then I may just do it that way.
Any chance to give me a hint on how you did the conditional hiding for Trac core you mentioned before? I guess, this could save me some time, but not a blocker for me either.
comment:6 follow-up: 7 Changed 13 years ago by
Owner: | changed from Steffen Hoffmann to Ryan J Ollos |
---|---|
Status: | assigned → new |
Sorry, didn't mean to take it away from you. :-)
comment:7 Changed 13 years ago by
Replying to hasienda:
Sorry, didn't mean to take it away from you. :-)
Please feel free to reassign. I just assigned it to myself to let everyone know I intended to implement. Once my part is done, it's all yours ;)
I'll get back to you with regarding your other question by tonight.
comment:8 Changed 13 years ago by
Owner: | changed from Ryan J Ollos to Steffen Hoffmann |
---|---|
Status: | new → assigned |
I could do an additional check in like
def process_request(self, req): req.perm.require('TAGS_VIEW') if 'q=' in self.env.config.get('mainnav', 'tags.href', '') and \ 'q' in req.args: # TRANSLATOR: The meta-nav link label. add_ctxtnav(req, _("Back to Cloud"), req.href.tags())
but I feel having the back-link isn't evil anymore, if we hide it when displaying the cloud.
comment:9 Changed 13 years ago by
(In [10748]) TagsPlugin: Hide 'Cloud' back-link, if showing TagCloud in '/tags', refs #9210.
Renaming the link to 'Back to Cloud' is more consistent with use of context navigation in Trac core (i.e. see TagsQuery). Thanks to Ryan for this idea.
comment:10 Changed 13 years ago by
(In [10751]) TagsPlugin: Hide 'Cloud' back-link on '/tags' page for empty tag queries too, refs #9210.
comment:11 Changed 13 years ago by
Replying to hasienda:
Any chance to give me a hint on how you did the conditional hiding for Trac core you mentioned before? I guess, this could save me some time, but not a blocker for me either.
I wasn't able to find the ticket I was trying to think of. I might be remembering incorrectly.
There might be an opportunity here a small amount of refactoring to improve the existing patches. I'll attach a patch for that now.
Changed 13 years ago by
Attachment: | th9210-r10751-0.11.7.patch added |
---|
comment:13 Changed 13 years ago by
(In [10755]) TagsPlugin: Hide simplify check to not duplicate existing logic, refs #9210.
Done as suggested by Ryan J. Ollos, thanks.
While initially I'd agree, clutter=defect is a bit harsh, and how about non-standard configuration like
so the ctxtnav entry would remain as the only way to quickly revert to tag cloud?
Still for the majority of installations the obsolete redundancy may be a valid claim. What do others think? At least I don't feel a strong need for yet another option here, right?
A bit far-fetched for such a small link - anyway: Should we detect tags.href<>"/tags" and hide/unhide that ctxtnav link accordingly?