> As the ticket said, I am contemplating an xhtmlVersion attribute. For
> example:
>
>
>
>
> (yes, 2.0 exists as a proposed spec!)
> The first two are equivalent. Otherwise, the version can
> dictate how attributes are rendered.
> What do you think?
Excellent! Thanks very much!
--
Tim Sl
problem arose.
>
> One poster said "Current browsers don't even handle XHTML 1.0 properly
> so moving to 1.1 isn't workable." There's a good deal of truth there,
> there's no browser I'm aware of that enforces strict xhtml compliance
> when it sees a
ent browsers don't even handle XHTML 1.0 properly
so moving to 1.1 isn't workable." There's a good deal of truth there,
there's no browser I'm aware of that enforces strict xhtml compliance
when it sees a DOCTYPE statement specifying xhtml. If a browser did
that, I think
And also:
https://issues.apache.org/struts/browse/STR-2598
Tim,
Please see https://issues.apache.org/struts/browse/STR-1665
Is this what you're looking for?
On 9/5/07, James Holmes <[EMAIL PROTECTED]> wrote:
>
> https://issues.apache.org/struts/browse/STR
>
>
> On Wed Sep 5 14:05 , 'Slattery, Tim - BLS' <[EMAIL PROTECTED]> sent:
>
> >> Please check the
https://issues.apache.org/struts/browse/STR
On Wed Sep 5 14:05 , 'Slattery, Tim - BLS' <[EMAIL PROTECTED]> sent:
>> Please check the ticket list for Struts 1.4. If you find this
>> very issue there (I think it is) and you need it in 1.3, I
>> can back port it for 1.3.10
>
>I don't know how to
> Please check the ticket list for Struts 1.4. If you find this
> very issue there (I think it is) and you need it in 1.3, I
> can back port it for 1.3.10
I don't know how to do that. I see no link on the Struts page to a
ticket list or to Struts 1.4.
--
Tim Slattery
[EMAIL PROTECTED]
---
Please check the ticket list for Struts 1.4. If you find this very issue
there (I think it is) and you need it in 1.3, I can back port it for 1.3.10
Paul
OK, I removed the attribute in the struts-html-el.tld in Struts
1.3.8, and it runs.
NowI'm trying to use xhtml. I use this:
And it generates this:
http://www.w3.org/1999/xhtml"; lang="en-US"
xml:lang="en-US">
The lang="en-US" is in there whether I specify lang="true", lang="false"
or omi
in, is this a reasonable
behaviour to introduce?
I realise that these changes could have impact on existing stylesheets;
would it make sense for the and tags to
accept an additional attribute specifying the level of XHTML compliance
to render for? This would obviously be a larger impact change (f
10 matches
Mail list logo
