I applied the changes I outlined below sometime last week, but forgot
to mention it here. Let me know if there is anything else that I
could/should add to the CFCs.
Cheers
G
On Fri, 16 Jul 2004 10:49:31 -0700, Deanna Schneider
<[EMAIL PROTECTED]> wrote:
> Woops, sorry, I didn't mean to have id in
Woops, sorry, I didn't mean to have id in the label. I meant that to be
title (like you were doing). ID shouldn't be in the label - just the input.
- Original Message -
From: "Greg Stewart"
> And I still get it wrong... :) I just checked with the
> webstandards.org website and they recom
Woops, sorry, I didn't mean to have id in the label. I meant that to be
title (like you were doing). ID shouldn't be in the label - just the input.
- Original Message -
From: "Greg Stewart"
> And I still get it wrong... :) I just checked with the
> webstandards.org website and they recom
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
| Sent: Wednesday, July 14, 2004 16:31
| > Just curious, what's the big advantage of XHTML compatible?
| You can perform XSLT on xhtml pages... which according to the
| XSLT cookbook (O'Reilly) for more details on how this is
| going to be very ha
ave to use the "for" attribute combined with the "id attribute:
> Your Name:
>
>
>
> - Original Message -
> From: "Greg Stewart"
> Subject: Re: CFForm, CFInput, etc not xhtml compatible!
>
> > I pesonally have never used the CFF
Or the onTap framework which has some extensive forms features, some
of which overlap what's available with qForms but provide integrated
server-side components which a purely _javascript_ API like qForms can't
provide. In particular the onTap framework's form library allows you
to specify a label
TED]
Sent: 14 July 2004 15:27
To: CF-Talk
Subject: RE: CFForm, CFInput, etc not xhtml compatible!
> I was just trying to make some of my pages xhtml 1.0
> transitional compatible and when I tested through the W3C
> testing page I noticed that cfform and the others capitalize
ed in the
label tag:
Your Name:
OR you have to use the "for" attribute combined with the "id attribute:
Your Name:
- Original Message -
From: "Greg Stewart"
Subject: Re: CFForm, CFInput, etc not xhtml compatible!
> I pesonally have never used the CFFORM t
> Ok, I have to say that I agree with not using the cfform,
> cfinput, etc. but I have a lot of legacy code. Some I wrote
> when I was just starting with cf and a lot of it that I
> inherited.
I suspect that this code isn't XHTML-compliant anyway, though, right? I know
the "legacy code" I've le
do, so fixes in a new
version can't help the problem now.
Sorry for the rant, but I had to get it out.
Steve
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 10:27 AM
To: CF-Talk
Subject: RE: CFForm, CFInput, etc not xhtml compatible!
> > Just curious, what's the big advantage of XHTML compatible?
>
> You can perform XSLT on xhtml pages... which according to the
> XSLT cookbook (O'Reilly) for more details on how this is
> going to be very handy in the future
>
> Some examples off the top of my head
> - XSL template to chang
> Just curious, what's the big advantage of XHTML compatible?
You can perform XSLT on xhtml pages... which according to the XSLT
cookbook (O'Reilly) for more details on how this is going to be very
handy in the future
Some examples off the top of my head
- XSL template to change specific XHTML
> I was just trying to make some of my pages xhtml 1.0
> transitional compatible and when I tested through the W3C
> testing page I noticed that cfform and the others capitalize
> the tags and don't self close them.
>
> Anyone else notice this?
>
> I would hate to have to recode all of my pa
> Just curious, what's the big advantage of XHTML compatible?
That's a good question, I think. Right now, the advantage is minimal if not
completely illusory. There aren't any devices out there which take advantage
of XHTML specifically, to my knowledge. So, in current browsers, XHTML is
functiona
>>I would hate to have to recode all of my pages when the directive comes down
>>to be xhtml compatible
Just curious, what's the big advantage of XHTML compatible?
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
I pesonally have never used the CFFORM tags, but the xHTML directive
is one of the reason's I have built up a form CFC so that I can cut
down a little on my form building and amke sure I don't forget any of
the attributes for xHTML/accessible forms... You can find them here:
http://gregs.tcias.co.u
16 matches
Mail list logo
