Though I'm not pro on this change, I suggest putting it in before rc1. Martijn
On 11/3/07, Al Maw <[EMAIL PROTECTED]> wrote: > Matej Knopp wrote: > > Fixing this has practical benefits. And I haven't heard one argument > > against it except that "wicket shouldn't do that because it's html". I > > have personally problems with such arguments. It just feels not > > pragmatic. > > We have three options here: > 1. Fix the issue transparently for the user. > 2. Tell the user they've made an error and how to fix it. > 3. Not give you any help at all. > > I'd argue that if it's possible to make stuff "just work" (i.e. #1) then > you should do. > > Computer/framework's job is to make things as easy as possible. If we > can tell you how to fix an issue, then the only possible argument for > not doing so automatically is if that's really hard, or if there's a > performance penalty in doing that. Given this scan would only happen > once per markup-file load, not on every page hit, it's probably fine > performance-wise. > > So, uh, we should just fix it transparently. > > Regards, > > Al > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
