Le 09/11/2011 11:23, Martin Grigorov a écrit :
- DataTable : a SPAN is always added in the TD and TH.
Override DataTable component and provide your own MyDataTable.html.
The .java code will just call super constructors.
As said before, I don't feel very confident in duplicating wicket code and
So you say that br/ is valid but link / is not.
Both of them are void elements. Why is this difference in handling them ?
Can you provide a link to specification where they say that link /
is invalid in HTML4 ?
On Wed, Nov 9, 2011 at 7:26 PM, pgoiffon.wic...@free.fr wrote:
in HTML the link tag has no end tag.
in XHTML the link tag must be properly closed.
source: http://www.w3schools.com/tags/tag_link.asp
.
On Thu, Nov 10, 2011 at 9:29 AM, Martin Grigorov mgrigo...@apache.org wrote:
So you say that br/ is valid but link / is not.
Both of them are void
I'm interested in a specification saying that link / is invalid in HTML4.
On Thu, Nov 10, 2011 at 10:39 AM, manuelbarzi manuelba...@gmail.com wrote:
in HTML the link tag has no end tag.
in XHTML the link tag must be properly closed.
source: http://www.w3schools.com/tags/tag_link.asp
.
On
in HTML the link tag has no end tag may it be enough to confirm
link/ is perfectly valid in html, and not the opposite.
.
On Thu, Nov 10, 2011 at 9:49 AM, Martin Grigorov mgrigo...@apache.org wrote:
I'm interested in a specification saying that link / is invalid in HTML4.
On Thu, Nov 10,
While I usually enjoy painting a bike shed, and this is one perfect
example of mine being green, the 4.01 specification is from 1999,
which is 12 years ago. While technically closing a link tag is
considered a validation error (I tried the html validator of w3c, see
below), in practice the HTML
Just to be clear: we live the xhtml validated markup dream and it
sucks. You can't use anything browsers have added since 2001. Stuff
that makes users happy: autofocus, placeholder text, no autofill. We
modified our xhtml validator to support these cases (and to choke on
other invalid markup)
Hi,
Le 10/11/2011 09:29, Martin Grigorov a écrit :
So you say thatbr/ is valid butlink / is not.
I thought that any self closing tag was invalid in any html version,
html 4 as of html 5.
But the validator is ok with self closing br and link in html 5, and the
html 5 draft recommandation
On Thu, Nov 10, 2011 at 3:41 PM, Pierre Goiffon
pierre.goif...@interview-efm.com wrote:
Hi,
Le 10/11/2011 09:29, Martin Grigorov a écrit :
So you say thatbr/ is valid butlink / is not.
I thought that any self closing tag was invalid in any html version,
html 4 as of html 5.
But the
Le 10/11/2011 10:33, Martijn Dashorst a écrit :
While technically closing alink tag is
considered a validation error (I tried the html validator of w3c, see
below), in practice the HTML 4.01 standard is really crippled, as are
the other HTML standards from that time.
Can you provide us some
Le 10/11/2011 14:58, Martin Grigorov a écrit :
I thought that any self closing tag was invalid in any html version,
html 4 as of html 5.
But the validator is ok with self closing br and link in html 5, and the
html 5 draft recommandation says very clearly self closing tags are
allowed for void
On Thu, Nov 10, 2011 at 4:34 PM, Pierre Goiffon
pierre.goif...@interview-efm.com wrote:
Le 10/11/2011 14:58, Martin Grigorov a écrit :
I thought that any self closing tag was invalid in any html version,
html 4 as of html 5.
But the validator is ok with self closing br and link in html 5,
Le 10/11/2011 16:11, Martin Grigorov a écrit :
I just tested link ... in Wicket 1.5 quickstart and it produced
link ... (no auto close of the start tag).
Can you explain your test ?
I'v just downloaded the wicket 1.5.2 package (zip version with sources)
and I see that
Le 08/11/2011 16:43, Martin Grigorov a écrit :
Hi,
Hello, thanks very much for your quick answer !
The problem is that there are several specifications and all of them
expect different output.
We try to stick to HTML5 because this is the future.
You mean, HTML 5 in Wicket 1.5 ? I tryed to
Hi,
On Wed, Nov 9, 2011 at 12:12 PM, pgoiffon.wic...@free.fr wrote:
Le 08/11/2011 16:43, Martin Grigorov a écrit :
Hi,
Hello, thanks very much for your quick answer !
The problem is that there are several specifications and all of them
expect different output.
We try to stick to HTML5
Martin Grigorov mgrigo...@apache.org a écrit :
The problem is that there are several specifications and all of them
expect different output.
We try to stick to HTML5 because this is the future.
You mean, HTML 5 in Wicket 1.5 ?
Yes, in Wicket 1.5.
Wicket 1.4.x branch receives only bug
pgoiffon.wic...@free.fr a écrit :
I was convinced that HTML5 is still HTML, so auto-closed tags are
invalid. I checked the html 5 draft recommandation this morning before
answering and can't find anywhere that auto closed tags are valid.
Found it !
Hello,
I'm working as a developper for a software company that build some
products using Wicket 1.4 (1.4.17 for the moment being).
I'm trying to improve accessibility in our online survey product. The
first thing I did was to check our pages with the W3C validator
(http://validator.w3.org),
Hi,
The problem is that there are several specifications and all of them
expect different output.
We try to stick to HTML5 because this is the future.
See below.
On Tue, Nov 8, 2011 at 5:17 PM, Pierre Goiffon pgoiffon.wic...@free.fr wrote:
Hello,
I'm working as a developper for a software
19 matches
Mail list logo
