Rename Back and Forward buttons,in Previous Conservations > Search Tab, to Previous and Next
Bug #618398 reported by
Vish
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Empathy |
Fix Released
|
Low
|
|||
| One Hundred Papercuts |
Fix Released
|
Low
|
Unassigned | ||
| empathy (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: empathy
In the empathy Previous Conversations window ,Search tab,
the buttons for finding/jumping to the next search item, the buttons are named "Back" and "Forward".
The labels are a bit awkward for a buttons which just allow user to jump to the next item .
It would be better to name those buttons as "Previous" and "Next"
Similar items are named as:
"Previous" and "Next" in Firefox [Chrome's tooltips mention as Previous/Next]
"Find Previous" and "Find Next" in Gnome's Log Viewer
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.6-0ubuntu1
| summary: |
- Rename Back and Forward buttons to Previous and Next + Rename Back and Forward buttons,in Previous Conservations > Search Tab, + to Previous and Next |
| Changed in empathy (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in hundredpapercuts: | |
| importance: | Undecided → Low |
| milestone: | none → maverick-round-3-social-networking |
| status: | New → Triaged |
| Changed in empathy: | |
| status: | Unknown → New |
Revision history for this message
| Vish (vish) wrote | #1 |
| Changed in empathy (Ubuntu): | |
| status: | Triaged → Fix Committed |
| Changed in hundredpapercuts: | |
| status: | Triaged → Fix Committed |
| Changed in empathy: | |
| status: | New → Fix Released |
Revision history for this message
| Omer Akram (om26er) wrote | #2 |
| Changed in empathy (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in hundredpapercuts: | |
| status: | Fix Committed → Fix Released |
| Changed in empathy: | |
| importance: | Unknown → Low |
To post a comment you must log in.
This has now been fixed upstream