Okay. Again. This is not about developer making error! Code like this: <div/> Something
Is perfectly legal. However, firefox interprets it as <div> Something ... Which is completely wrong. This is not correcting developer error! This is correcting browser error. And such thing is very difficult to spot. -Matej On 11/2/07, Philip A. Chapman <[EMAIL PROTECTED]> wrote: > I agree with this stance. > > On Fri, 2007-11-02 at 09:19 -0600, John Ray wrote: > > I got bit by this problem yesterday. Although I was just previewing the > > page in the browser by loading the HTML file directly. Since Wicket > > wasn't running it wouldn't have mattered if it fixed my div tag for me > > or not. > > > > I'd rather see Wicket not modify the HTML as it's then starting down the > > slippery slope of assuming the developer made an error and automatically > > correcting it. I think a better solution would be to have an option > > where Wicket looks for potential errors in your HTML and then outputs a > > warning to the console. > > > > John > > > > Gwyn Evans wrote: > > > It seems to me that while it's something that Wicket /could/ do, I'm > > > not sure if it's something that Wicket /should/ do... > > > > > > Having said that, I think I'd be less against it if we restricted it > > > to only tags that had a "wicket:id" attribute? > > > > -- > Philip A. Chapman > > Desktop and Web Application Development: > Java, .NET, PostgreSQL, MySQL, MSSQL > Linux, Windows 2000, Windows XP > > >
