[ZBX-3304] item filter control visual discrepancy Created: 2010 Dec 17  Updated: 2017 May 30  Resolved: 2012 Feb 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.9.1 (alpha)
Fix Version/s: 2.0.0rc1

Type: Incident report Priority: Minor
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: itemconfigfilter, items, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

trunk rev 16226


Attachments: PNG File item_filter_buttons.png    
Issue Links:
Duplicate
duplicates ZBXNEXT-903 Redesign Configuration->Items Closed

 Description   

item configuration filter buttons "filter" & "reset" should be visually unified (although maybe the 'reset' one might have a faint red background or somesuch)



 Comments   
Comment by Alexey Fukalov [ 2011 Mar 29 ]

i like current style, button assumes we submit something, but Reset only clear fields.. and it's easy distinct them

Comment by richlv [ 2011 Mar 29 ]

hmm. can't agree
they look awfully different visually, are misaligned and it's not clear enough that they both are operation controls.

i'd say we should make them both buttons. if a visual distinction is needed, we could introduce/use some button colouring - similar to how we do in entity properties with that slightly yellowish border

Comment by Aleksandrs Saveljevs [ 2011 Mar 30 ]

Also note that "filter" in English can be both a noun and a verb. So when translating into Latvian you have to choose between either "Filtrs" or "Filtrēt". As far as I remember, both nouns and verbs are used in the frontend in different circumstances. Can something be done about distinguishing nouns from verbs?

<richlv> missing context function handled at ZBX-3271 (probably a blocker for 2.0 ?)

Comment by Eduards Samersovs (Inactive) [ 2012 Jan 28 ]

Resolved in ZBXNEXT-903

Comment by Alexei Vladishev [ 2012 Jan 30 ]

Reopening, should be closed only after proper testing.

Generated at Fri Mar 29 16:53:41 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.