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 fixes and only major ones.
I say that in Wicket.current we try to follow HTML5 recomendations.
There is no sense to start supporting all the versions of HTML 4
standards (strict, loose, ...) when even the browser vendors agreed
that this doesn't work and they have to maintain just one
specification.
I'm confused with this statement : what do you mean by "supporting all
the version of HTML 4 standards" ? Wicket lets you put whatever
doctype you want, and send to the user agents any tag you may want to
use. The only problem I had with wicket considering html validation is
the way some tags in certain components are closed : valid in xhtml
but invalid in both transitionnal or strict html 4.
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. But
I've just use the validator with this markup :
<!DOCTYPE HTML>
<html>
<head>
<title>Testing tag closing</title>
</head>
<body>
<p>A paragraph with a auto-closed br<br />
Done !</p>
</body>
</html>
And it's stated as valid html 5 !
So if it is right and not just a validator bug (seems unlikely), I
suppose you meant, as your idea is to do html 5 with Wicket 1.5 and
plus, that auto closed tags will always be sent by Wicket ? Am I right ?
If so, for what I know now on, if it's too hard to add a mean for the
developpers to pick the way he wants the tag to be closed, then I
would recommend Wicket to close tags in the HTML way and forgive about
XHTML auto-closed tags. Thus Wicket will be compatible with all HTML
versions, up to 5 included. I don't think so much web site / app use
XHTML nowdays ?
1.4.x is close to its end of life. Soon we will stop porting fixes and
only security fixes will be committed in this branch.
We didn't get in that migration yet, we're finishing some of our
products major versions. It will certainly be the first step after
those products shipping :)
Though with just a quick view as we add, there seems to be a great
amount of efforts to produce to get existing apps to the 1.5 version ?
We'll see when the moment comes.
- DataTable : a SPAN is always added in the TD and TH.
Is there a way to change those span to
div in future versions of Wicket ?
Sure. File a ticket in Jira.
We cannot change it in 1.5.x because it may break silently apps in
production. So it will have to wait Wicket.next.
Will do :)
But I'm a bit sad about the perspective of resolution which seems
quite fareway. If the correction is just to change span to div, all
the possible troubles for existing apps I see are about css selectors
that wouldn't be right anymore (in css but eventually other areas -
see $() in jQuery).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
