incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject [Apache Bloodhound] #137: Correcting button classes - Phase 2
Date Fri, 13 Jul 2012 17:29:23 GMT
#137: Correcting button classes - Phase 2
 Reporter:  gjm        |      Owner:  nobody
     Type:  defect     |     Status:  new
 Priority:  major      |  Milestone:  Release 2
Component:  dashboard  |    Version:
 Keywords:             |
 #36 covered a number of changes to the bootstrap classes applied to

 This ticket is to continue that work and, in particular get careful and
 consistent use of the classes for buttons.

 From jdreimann's [
 bloodhound-dev/201207.mbox/%3CCAKoya91iQ512v3Xucia9-X9uKwoHAW81FJc_9Jg email]

 > I would like to suggest a few things regarding the buttons throughout
 the application:
 > 1. They should all be plain (class btn) unless it can be justified why
 they should be of any other style. See below for criteria.
 > 2. Primary actions should always be more prominent than secondary
 >    One specific example is that while editing a wiki article the user is
 more likely to want to submit changes then to cancel. It's why he/she
 started editing the article for in the first place.
 > 3. Prefer safe actions.
 >    Again in relation to wikis, it's easy to delete a version that has
 been submitted accidentally. If the user accidentally clicks cancel, all
 edits have to be rewritten. That causes grief. Nevermind deleting a page
 > In practice this could be implemented by making the Submit changes
 button more prominent (btn-primary), while potentially styling the Cancel,
 Delete version and Delete page buttons like links, which appear less
 prominent than buttons.

Ticket URL: <>
Apache Bloodhound <>
The Apache Bloodhound (incubating) issue tracker

View raw message