incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #206: Ticket fields layout broken if custom textarea fields are declared
Date Wed, 03 Oct 2012 20:10:05 GMT
#206: Ticket fields layout broken if custom textarea fields are declared
------------------------+-----------------------------------
  Reporter:  olemis     |      Owner:  olemis
      Type:  defect     |     Status:  accepted
  Priority:  blocker    |  Milestone:  Release 2
 Component:  ui design  |    Version:
Resolution:             |   Keywords:  ticket field textarea
------------------------+-----------------------------------

Comment (by olemis):

 Replying to [comment:7 jdreimann]:
 > Ok, in brief I think we should move back to something closer to
 [http://trac.edgewall.org/demo-0.12/ticket/3000 Trac's layout] for these
 fields.
 > Two columns of **Key: Value** pairs.
 >

 I think full row is necessary for textarea fields . If using two columns
 layout width will vary depending on whether Activity feed is available or
 not . Is that the idea ?

 > I came to that conclusion by the problems described in this ticket, but
 also thinking about how a [https://issues.apache.org/bloodhound/ticket/217
 responsive layout] may work in the future.
 >

 Current solution makes field UI more concise which is good for responsive
 designs , isn't it ?

 [...]

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/206#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message