[GitHub] [wicket] papegaaij commented on issue #401: WICKET-6726: remove inline styling and javascript from Form

2020-01-23 Thread GitBox
papegaaij commented on issue #401: WICKET-6726: remove inline styling and javascript from Form URL: https://github.com/apache/wicket/pull/401#issuecomment-578028265 I've restored the configurable class names (and did the same thing in component for the placeholder). Personally, I still do

[GitHub] [wicket] papegaaij commented on issue #401: WICKET-6726: remove inline styling and javascript from Form

2020-01-23 Thread GitBox
papegaaij commented on issue #401: WICKET-6726: remove inline styling and javascript from Form URL: https://github.com/apache/wicket/pull/401#issuecomment-577890877 I totally understand the use case for configurable css classes in cases I see as 'user facing': elements a user will need to

[GitHub] [wicket] papegaaij commented on issue #401: WICKET-6726: remove inline styling and javascript from Form

2020-01-22 Thread GitBox
papegaaij commented on issue #401: WICKET-6726: remove inline styling and javascript from Form URL: https://github.com/apache/wicket/pull/401#issuecomment-577531197 @svenmeier I didn't remove the changes for WICKET-6527, only a very small part of it, namely the customizable classname. In