>>The following tags are lenient: p, br, img, input, hr, link, meta. But
>>if I were you I'd realy try to make my markup xhtml compliant. It is
>>much easier to find bugs like yours besides that browsers are not
>>consistent in the way they treat none-closed tags. Might be that I'm
>>wrong, but I guess no browser knows what you mean by <tr><tr>.
>>if I were you I'd realy try to make my markup xhtml compliant. It is
>>much easier to find bugs like yours besides that browsers are not
>>consistent in the way they treat none-closed tags. Might be that I'm
>>wrong, but I guess no browser knows what you mean by <tr><tr>.
yeah accepted...i actually used Dreamweaver which generates XHTML compliant code..i must have messed up some tags up while working in code view....
Wicket will be great with an IDE support cuz i can imagine a Wicket Bench IDE pre-parsing my HTML (notifiying me of these kind of errors) and then building up the corresponding Wicket Special Tags in a Tree form in one window of the IDE where you can relate with it in all forms of ways..that will be cool..well cooler cuz wicket in itself is cool enough anyway.
On 2/21/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
The following tags are lenient: p, br, img, input, hr, link, meta. But
if I were you I'd realy try to make my markup xhtml compliant. It is
much easier to find bugs like yours besides that browsers are not
consistent in the way they treat none-closed tags. Might be that I'm
wrong, but I guess no browser knows what you mean by <tr><tr>.
Juergen
On 2/21/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> It doesn't have to be completely XHTML compliant. For some tags we are
> more lenient. Juergen knows best on what tags that are precisely, but
> I can imagine that <br> and <p> are tags that fall in the category.
>
> The best way of developing applications is of course to be XHTML
> compliant, as this will be rendered best by all browsers, and you
> don't have to 'trust' different error recovery methods by the major
> vendors.
>
> Martijn
>
> On 2/21/06, Ayodeji Aladejebi <[EMAIL PROTECTED] > wrote:
> > aah right i see it...but really, must the HTML file be actually XHTML
> > compliant to work with wicket?
> >
> >
> > On 2/20/06, Gili < [EMAIL PROTECTED]> wrote:
> > >
> > > Doh! Turns out this is a user-error because I should be using
> > > WebMarkupContainer instead of WebComponent. The error message is very
> > > misleading though, can we fix that? It should say "WebComponent may not
> > > have a body" or something like that... I can file a bug report for it if
> > > you wish.
> > >
> > > Gili
> > >
> > > Gili wrote:
> > > >
> > > > I'm seeing this too. I have a page works properly but if I insert:
> > > >
> > > > <div wicket:id="noImages" id="noImages">No images</div>
> > > >
> > > > into my code suddenly I get a parsing error message from Wicket. It
> > > > isn't identical to the one reported by Ayodeji. He got:
> > > >
> > > > wicket.markup.MarkupException: Tag '<tr>' (line 40, column 21) has a
> > > > > mismatched close tag at '</table>' (line 184, column 17)
> > > >
> > > > whereas I get:
> > > >
> > > > 01:34:20,688 ERROR RequestCycle:964 - Expected close tag for <div
> > > > wicket:id="noImages" id="noImages">
> > > > [markup =
> > > >
> > file:/C:/Documents%20and%20Settings/Gili/My%20Documents/blueeye/trunk/desktopbeautifier/Server/netbeans6.0/build/web/WEB-INF/classes/desktopbeautifier/web/gallery/Page.html,
> > > > index = 88, current = [Raw markup]]
> > > > wicket.markup.MarkupException: Expected close tag for <div
> > > > wicket:id="noImages" id="noImages">
> > > >
> > > > If I comment out the <div> from the HTML code it works fine. If I
> > > > uncomment it, I get the above exception again. That's got to be a bug
> > > > right? Also, I noticed I only get this exception if I bind the <div> to
> > > > a WebComponent. If I bind it to a Label instead it works fine.
> > > >
> > > > On an unrelated note, the junit tests fail on ObjectsTest; you might
> > > > want to fix that.
> > > >
> > > > Gili
> > > >
> > >
> > > --
> > > http://www.desktopbeautifier.com/
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> > files
> > > for problems? Stop! Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> > >
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > > _______________________________________________
> > > Wicket-user mailing list
> > > Wicket-user@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wicket-user
> > >
> >
> >
> >
> > --
>
> --
> Living a wicket life...
>
> Martijn Dashorst - http://www.jroller.com/page/dashorst
>
> Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
