Using a SPAN element is completely arbitrary.  If you're worried about
markup formatting semantics in the template, then just use another
element.

You _could_ enounter all kinds of validation errors by putting tables
inside of spans (block element inside inline element is invalid), but
you can just as easily use DIV elements instead.

Woring inside of Tables? Use extra TBODY elements.

Also, judicious use of <option jwcid="<at>Foreach" element="option" ... 
can be helpful.

The beauty of templates is that they have just enough support to get
them rendering correctly in working/design environments. They're really
not meant to validate. Case-in-point : jwcid isn't a valid attribute on
any element.

</bd>

-----Original Message-----
From: Blackwings [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 17, 2006 2:13 AM
To: Tapestry users
Subject: Template header DOCTYPE

Hi,

I noticed something interresting about DOCTYPE. In fact, if a designer
give
me a XHTML1.0 transitional compliant html template, when I mark the tag
and
add some tags <span> the html is not anymore compliant :

<select jwcid="[EMAIL PROTECTED]" id="searchCriteria.requester" name="
searchCriteria.requester" size="1" tabindex="6" class="comboBox9pt">
   <span jwcid="@Foreach" source="ognl:requesters" value="ognl:
searchCriteria.requester">
      <option value="1" jwcid="@Option"
label="ognl:requesters.requesterCode
">elem1</option>
      <option value="2" jwcid="$remove$">elem2</option>
      <option value="3" jwcid="$remove$">elem3</option>
      <option value="4" jwcid="$remove$">elem4</option>
    </span>
  </select>

The <span> cannot be place after a <select> and this is warned.

I have the same problem when I want to mark a bloc of <tr>, not all, in
a
<table>. I have to put a <span> tag between to a </tr> and a <tr> that
is
not "permit" by the DOCTYPE definition, normally.

Is there another DOCTYPE that manage "Tapestry template" or do we have
to
let the warn like that?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to