papegaaij edited a comment 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 style because Wicket will not. This case, I would say, is different. Here, Wicket provides the styling, and we need to make sure it does not clash with user styling. This is why these classes are prefixed with a `wicket--` namespace. Of course, we can make these classnames configurable as well, but here I do not see the need. Changing the classname will break the styling, so a user will need to supply it's own styling. But when you are supplying your own stylesheets anyway, why not use the classnames we picked?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
