tel8618217223380 / prado3

Automatically exported from code.google.com/p/prado3
Other
0 stars 0 forks source link

strange behaviour with thtmlarea #196

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.create page with thtmlarea with all options
2.add iframe eg to google on the same page
3.thmlarea becomes a normal text box 
4.Comment out the iframe and thtmlarea works as before

What is the expected output? What do you see instead?
see points 3 and 4 above

What version of the product are you using? On what operating system?
3.1.5 on centos 5.1 apache webserver. Occurs in both ie 8 and firefox 3.5

Please provide any additional information below.
haven't built a test site to check but this is what happens on our page. 
If you can't reproduce please let me know and I'll knock together a test 
page for this. Very strange but noticed when added iframe for live preview 
page to an existing working site.

Original issue reported on code.google.com by kactus...@gmail.com on 17 Aug 2009 at 7:45

GoogleCodeExporter commented 9 years ago
Hi just wanted to add a point that it looks like it has something to do with 
the 
tags. I changed on of the frames to a TInlineFrame and the htmlarea worked I 
enabled 
the iframe above it and it continued to work. 

However iframe below the tinlineframe would cause the same behavior as reported 
above.

So to summarise:
<tr><td>thtmlarea</td><tr>
<tr><td>iframe</td><tr>
<tr><td>tinlineframe</td><tr>
works as expected

however:
<tr><td>thtmlarea</td><tr>
<tr><td>tinlineframe</td><tr>
<tr><td>iframe</td><tr>
does not

I can put several iframes between the thtmlarea and the tinlineframe and it 
continues to work.

Hope that give you guys enough info to knock it for 6
cheers - Kactus

Original comment by kactus...@gmail.com on 18 Aug 2009 at 2:32

GoogleCodeExporter commented 9 years ago
ok Sussed it

was using <iframe src="asdf" />
instead of
<iframe ... > </iframe>
the tinlineframe adds the </iframe> to the end and the page is processed

noticed when examining the source. 
Cheers - Kactus

Original comment by kactus...@gmail.com on 18 Aug 2009 at 3:26

GoogleCodeExporter commented 9 years ago
Thanks for the report Kactus, I'm glad you solved it :)

Original comment by carlgmathisen on 18 Aug 2009 at 2:07