FumingDing / embeddedjavascript

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

<h1>,<h2>,<h3> in templates cause "unspecified" error in i.e. 7. #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create an ejs template that uses the [%%] style tags
2. add an <h3> (or any heading tag 1-5) to the template
3. render template

What is the expected output? What do you see instead?
internet explorer gives "unspecified error".  FF/chrome/safari all fine.

What version of the product are you using? On what operating system?
1.0 on PC/internet explorer, and Mac safari/ff/chrome

I have verified, definitively that explorer can't render ejs templates that
include heading tags with numbers in them (i.e. h1, h2, etc.)  working
around by using custom p tags.

Original issue reported on code.google.com by ReadySet...@gmail.com on 8 Mar 2010 at 8:05

GoogleCodeExporter commented 8 years ago
Have you tried closing the tags?  I'm pretty sure if you insert correct HTML, 
it should 
work.

Marking it as WontFix until I hear back.

Original comment by JustinBMeyer@gmail.com on 12 Mar 2010 at 3:21

GoogleCodeExporter commented 8 years ago
I can confirm this behavior.  With both an opening and closing header tag (and 
nothing else in the template) I receive an "Unknown runtime error" in IE 7.  
This is the content of my ejs file:

 <h1>fail</h1>

I'll poke around a bit more. The line given is 120 when setting the 
element.innerHTML (I verified the render works correctly).  As a matter of fact 
simply setting the innerHTML to:
  <h1>fail</h1>  
as a hard coded string with an emplate template will cause the same error.

Apparently IE7 doesn't like the H1 tag inside of a DIV tag.  If you change the 
target render area to be (for example) the body tag itself, then everything 
works... since the body tag is obviously allowed to have h1 tags in it.

Not as useful as targetting a div, and as far as I knew divs can contain h1 
tags.

Original comment by ackl...@gmail.com on 4 Jan 2012 at 9:36