What browser are you using?

CFForm in CF7 does produce valid XHTML, Sean's comment was from the CF6
days. What are you seeing that is not xhtml compliant?

It sounds like your flash forms are including both the <object> and
<embed> tags, which is not xhtml compliant. 

We do some browser detection to determine if we need to output an object
tag (IE) or an embed tag (Firefox) , instead of doing that old non-xhtml
shortcut of putting the embed tag inside of the object tag. However just
to be safe we do output both if we can't detect your browser correctly.


---nimer

-----Original Message-----
From: Sebastian Mork [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 23, 2005 10:55 AM
To: CF-Talk
Subject: Re: xhtml and cfform flash

Hi,

I mean the code that is generated for flash-forms like..
'<embed pluginspage='http://www.macromedia.com/go/getflashplayer' ");
id='CFForm_1' ");   .......'

validator gives a lot of errs like 'there is no attribute
"pluginspage"'.

I read somewhere that you either use cfform(flash) or xhtml, right?
No other possibilities yet?

In another post I wrote what I've read (from Sean Corfield) in the
livedocs:
(http://livedocs.macromedia.com/wtg/public/coding_standards/style.html
-- near the bottom)
"SeanCorfield said on Jul 22, 2004 at 10:14 AM : 
The non-compliance of code generated by CFFORM is a known issue that
will be addressed in a future release. "

So, I've to wait..... or what?

--
Sebastian Mork
[EMAIL PROTECTED]
--

On Thu, 23 Jun 2005 10:08:24 -0400
S. Isaac Dealey <[EMAIL PROTECTED]> wrote:

> > Hi,
> 
> > what about flash-forms and valid xhtml?
> > is there a way to create valid xhtml-code by cfform??
> 
> Heh... I believe you're actually the 2nd person to ask that this
> morning...
> 
> Are you referring to the capitalized xhtml elements?
> 
> I haven't worked with CF7's CFFORM tools myself (I have something
> better) but I would expect you could make a copy of the default XSL
> sheet and modify it to produce lower-case elements. Or modify the
> default XSL sheet. I know the default sheet has a bug in it that
> causes multiple-select elements to be un-selected if they should be
> prepopulated with multiple elements selected, so there's a good chance
> you would need to edit the default XSL sheet anyway. Here's the url
> for that fix:
> 
> http://blog.web-shorts.com/?day=3/6/2005
> 
> He does mention that it's in _formelements.xsl ... although offhand I
> don't know where that file is located... I'd expect it's under the
> cfusionmx webroot directory somewhere but it's probably documented in
> the livedocs. http://livedocs.macromedia.com
> 
> hth
> 
> s. isaac dealey   954.522.6080
> new epoch : isn't it time for a change?
> 
> add features without fixtures with
> the onTap open source framework
> 
> http://www.fusiontap.com
> http://coldfusion.sys-con.com/author/4806Dealey.htm
> 
> 
> 
> 
> 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:210535
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to