Opened 11 years ago
Last modified 11 years ago
#11232 new enhancement
The favicon could show the status of the page
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | unscheduled |
| Component: | rendering | Version: | |
| Severity: | trivial | Keywords: | ui icon |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
The favicon.ico could be used to reflect the current status of the project.
If the project currently does have serious bugs, it could be rendered in red, while if everything is OK, it could be rendered in green.
I suggest putting a small colored bulb on the icon.
Imho the favicons are usually cached by the browsers, but are updated as soon as you visit the page again.
So this would not make for an automated notification, but it would reflect the state when you last visited trac.
I usually place a link to trac on my bookmarks bar, It would be nice to use that as a reminder of the current state.
In the /report/ section it should reflect the color of the topmost entry displayed. This could also work with custom reports.
It might also be useful for the /ticket/ section. when a ticket is closed, a green checkmark might be added to the icon.
How to implement that?
- Deliver the favicon on a url related to the page (aka /report/1/icon.ico)
- add a filter to modify the icon, based on the context available at that page
enjoy!
Attachments (0)
Change History (4)
comment:1 by , 11 years ago
| Description: | modified (diff) |
|---|
follow-up: 4 comment:2 by , 11 years ago
comment:3 by , 11 years ago
| Milestone: | → unscheduled |
|---|
comment:4 by , 11 years ago
Replying to rjollos:
It is nice idea, but too much of a niche feature to add to Trac in my opinion.
I don't agree.
For example, how would you define serious bug, and how many options would we need to add to accommodate user preferences for serious bug? You could most likely implement it via a plugin though, and th:ContextChromePlugin comes to mind.
Being able to assign one of x (5, 6?) favicons to a ticket resolution sounds like a neat thing to do.
It is nice idea, but too much of a niche feature to add to Trac in my opinion. For example, how would you define serious bug, and how many options would we need to add to accommodate user preferences for serious bug? You could most likely implement it via a plugin though, and th:ContextChromePlugin comes to mind.