[X] Other suggestion: don't have a class on the span, or even better, don't have the span element at all inside the list-item
For any customisations beyound this, just create your own FeedbackPanel, it's easy and gives complete control. On Sun, Oct 28, 2012, at 17:03, Sebastien wrote: > Hi, > > To sum-up this thread: we have a (not huge, but still) design issue that > annoys several users. A patch* has been provided but some questions > remains... > Given this, I would suggest a kind-of vote about the several points > discussed earlier, in order to enlighten the dev-team about the preferred > choice of their (beloved) users.** > > Here are some possible options: > [ ] Please apply the patch as-is. It currently provides 2 methods > (#getListCSSClass and #getLabelCSSClass), #getCSSClass is marked a > deprecated until marked as private (or removed) > [ ] Do not apply the patch as-is, #getCSSClass should be kept (not marked > as deprecated) > [ ] Do not apply the patch as-is, I do not agree with the 2 method names. > I > would have preferred: (please specify) > [ ] This is not an issue; this does not need to be "corrected" > [ ] Other suggestion: (please specify) > > Thanks in advance for your contribution, > Sebastien > > (*) https://issues.apache.org/jira/browse/WICKET-4831 > (**) Sure, dev-team opinion is also kindly asked! :) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
