The problem that Lenya validates a document as a "Strict" document type, but
this stuff will be fine if we will validate FCKEditor out as a "Transitional"
document type.
I've tried this code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<title>test</title>
</head>
<body>
<form action="send" method="get" name="mform">
<input name="msubmit" type="submit" value="submit" />
</form>
</body>
</html>
in W3C validator (http://validator.w3.org/check). Validation was passed.
Are there any way to switch validation rules to "Transitional" document type?
Richard,
What do you think about that?
Best regards,
Oleg Barmin.
________________________________________
From: Richard Frovarp [[email protected]]
Sent: Tuesday, October 06, 2009 10:34 AM
To: [email protected]
Subject: Re: Problem with FCKEditor and new form
Oleg Barmin wrote:
> Hi,
>
> I try to add new form to the publication using FCKEditor. Click form icon.
> Give it a name (mform) and an action (send). Place a send button on a form
> (name - msubmit, text - send). Click save in editor and get multiple errors:
>
> Popup with error: "Error: The TEXTAREA with id or name set to "content" was
> not found"
> And errors on page:
>
>
> * error: attribute "name" not allowed at this point; ignored
> * error: element "input" from namespace "http://www.w3.org/1999/xhtml";
> not allowed in this context
> * error: unfinished element
>
> What's the problem with it?
>
> Best regards,
> Oleg Barmin.
>
Using the demo editor, I see the following code being generated:
<form action="send" method="get" name="mform">
<input name="msubmit" type="submit" value="submit" />
</form>
The input tag needs to be wrapped inside of a p tag. So, the editor is
generating invalid syntax. You can get around it by hitting enter in the
form area after first creating a form, but before adding form elements.
The FCK module passes its contents through the clean xslt and a change
could be made there to make sure the form content is wrapped in a p or
similar tag.
I did the last round of compatibility with FCKEditor, and we never had a
need for forms, so that part was never tested. I've posted a bug to
remind me for the next time I have time to work on this. If you come up
with a solution, feel free to pass it along.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
