Nested TextArea Woes!

[Bill]

I've got web-based forms to manage my online content. New HTML content is put online
using forms. Body text is inputted in the <TEXTAREA> as straight text.

Well, for the content of one of the pages, I decided to put an online survey - a form.
Problem is, this survey also contains a <textarea> area.

My online content management system is seeing the closing </textarea> in the content,
and is using it to close the <TEXTAREA> for the content management system. And so,
everything after that looks ugly. Ouch!

Can anyone please tell me how to manage this problem???

Bill.

 

[Jens Peter Karlsen [FP-MVP]]

Maybe if you had told us which CMS system. But what has this to do
with Frontpage?
Try support for the CMS you use.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.

 

[Bill]

The pages are constructed using FP2000, then the HTML is copied into the textarea of the
CMS. This way, I have the advantage of FrontPage's WYSIWYG.

Which CMS system??? It's a custom... No offense, but if you understood this problem,
you'd realize that's irrelevant to the issue. It's all the same HTML, isn't it???

 

[Jens Peter Karlsen [FP-MVP]]

No, it is not irrelevant since it is a problem with how the CMS parses
the HTML.
What is irrelevant, is that you used FP to create the html you pasted
into the CMS. You could have used any other editor and you would have
had exactly the same problem with textarea tags

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.

 

[Bill]

No, it is not irrelevant since it is a problem with how the CMS parses
the HTML.

Wow, that's a dumb and ignorant thing for you to write. NO, the problem is how BROWSERS
parse HTML! A CMS does not "parse" HTML - a web server cannot parse HTML - *browsers*
parse HTML!

It's very clear that you do not understand this issue, so let me explain it to you:

<TEXTAREA class="editor">
<TEXTAREA class="content">
</TEXTAREA>
</TEXTAREA>

The first time you close the textarea, you close the first one with class="editor". The
second closing tag is totally ignored. Understand now?

This happens in any browser (go ahead - test it in FrontPage). Google "nested textarea"
and you'll see what I mean. Understand?

There is a tag called <nested:textarea> but I can't find any documentation on it.

Are you able to understand this issue now?

What is irrelevant, is that you used FP to create the html you pasted
into the CMS. You could have used any other editor and you would have
had exactly the same problem with textarea tags

Um, aren't you contradicting yourself???

First you claim "it's a problem with how the CMS parses the HTML", and now you claim...
what?

 

[Bob Lehmann]

Speaking of dumb and ignorant things to do...
Why are you pasting a <textarea> inside of a <textarea>?

This - nested:textarea - leads me to believe that you are in over your head
attempting to modify a Struts Framework application.

Bob Lehmann

No, it is not irrelevant since it is a problem with how the CMS parses
the HTML.

Wow, that's a dumb and ignorant thing for you to write. NO, the problem is how BROWSERS
parse HTML! A CMS does not "parse" HTML - a web server cannot parse HTML - *browsers*
parse HTML!

It's very clear that you do not understand this issue, so let me explain it to you:

<TEXTAREA class="editor">
<TEXTAREA class="content">
</TEXTAREA>
</TEXTAREA>

The first time you close the textarea, you close the first one with class="editor". The
second closing tag is totally ignored. Understand now?

This happens in any browser (go ahead - test it in FrontPage). Google "nested textarea"
and you'll see what I mean. Understand?

There is a tag called <nested:textarea> but I can't find any documentation on it.

Are you able to understand this issue now?

What is irrelevant, is that you used FP to create the html you pasted
into the CMS. You could have used any other editor and you would have
had exactly the same problem with textarea tags

Um, aren't you contradicting yourself???

First you claim "it's a problem with how the CMS parses the HTML", and now you claim...
what?




the textarea of
the content is put
online

content,

 

[Murray]

Such an attitude. And asking for help, too....

 

[Chris Leeds, MVP-FrontPage]

Yah, Jens is real stupid. Doesn't even know about HTML... LOL

--
Chris Leeds,
Microsoft MVP-FrontPage

If you make web sites for other people, you should check out ContentSeed:
http://contentseed.com/
--

 

[Stefan B Rusynko]

No it isn't irrelevant to the issue
Normally you can't nest a form w/i a form

A properly designed CMS would understand how to encode html (your added textarea tag / form)
to allow adding a form (w/i your forms based interface)
See http://www.innovastudio.com/editor_features.asp

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| The pages are constructed using FP2000, then the HTML is copied into the textarea of the
| CMS. This way, I have the advantage of FrontPage's WYSIWYG.
|
| Which CMS system??? It's a custom... No offense, but if you understood this problem,
| you'd realize that's irrelevant to the issue. It's all the same HTML, isn't it???
|
|
| "Jens Peter Karlsen [FP-MVP]" wrote...
| > Maybe if you had told us which CMS system. But what has this to do
| > with Frontpage?
| > Try support for the CMS you use.
| >
| > Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
| >
| >
| >
| > > On Wed, 23 Nov 2005 15:27:22 -0500, "Bill" wrote:
| >
| > >I've got web-based forms to manage my online content. New HTML content is put online
| > >using forms. Body text is inputted in the <TEXTAREA> as straight text.
| > >
| > >Well, for the content of one of the pages, I decided to put an online survey - a
| form.
| > >Problem is, this survey also contains a <textarea> area.
| > >
| > >My online content management system is seeing the closing </textarea> in the content,
| > >and is using it to close the <TEXTAREA> for the content management system. And so,
| > >everything after that looks ugly. Ouch!
| > >
| > >Can anyone please tell me how to manage this problem???
| > >
| > >Bill.
| > >
| > >
| > >
| > >
| > >
|
|

 

[Jens Peter Karlsen [FP-MVP]]

It is described very well how Browsers should parse HTML so it would
only be a problem if one or more browsers didn't do as they should.
That is not the case here, nesting a textarea is invalid.
If a CMS allows input of HTML it must also parse it so that it is
ensured that the final HTML that is presented to the browser is valid.
In this example it should have told you that nesting of textarea tags
is invalid. Because the parsing is rather complex most CMS I know
about doesn't allow HTML tags. Why the CMS you use allows it I don't
know.
I also don't know why you are dragging the server into this. As you
write, the server doesn't parse the HTML it just present it to the
Browser.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.

 

[Bill]

Speaking of dumb and ignorant things to do...
Why are you pasting a <textarea> inside of a <textarea>?

This - nested:textarea - leads me to believe that you are in over your head
attempting to modify a Struts Framework application.

Bob Lehmann

I know that if you do a Google for "nexted textarea", you come up with results relating
to something called Struts Framework. That is not what I'm using.

 

[Bill]

It is described very well how Browsers should parse HTML

That's why, when on 11/23, you had written "it is a problem with how the CMS parses the
HTML.", you were already wrong. Now, you contradict yourself???

so it would
only be a problem if one or more browsers didn't do as they should.
WHAT???

That is not the case here, nesting a textarea is invalid.
If a CMS allows input of HTML it must also parse it so that it is
ensured that the final HTML that is presented to the browser is valid.
No.

In this example it should have told you that nesting of textarea tags
is invalid.

No, what you really mean is that YOU do not know how to nest textarea tags.

Because the parsing is rather complex most CMS I know
about doesn't allow HTML tags. Why the CMS you use allows it I don't
know.

MOST available CMS allow HTML tags!!!

I also don't know why you are dragging the server into this. As you
write, the server doesn't parse the HTML it just present it to the
Browser.

Um, the CMS is on the server, right? Neither the server, nor the CMS, can "parse" HTML,
because parsing HTML means displaying the parsed data. And only the browser can do that,
right?

That's why, when on 11/23, you had written "it is a problem with how the CMS parses the
HTML.", you were already wrong.

But, that's besides the point. What I deeply object to is you signing yourself off as an
MVP and giving out bad answers. It fosters distrust in the system.

I have never, ever had an MVP give me a bad answer before you.

- Bill
(I'm just an MCP in FrontPage)