Comments on: We all love innerHTML http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/ Web development and Internet trends Sun, 20 Jul 2008 19:14:59 +0000 http://wordpress.org/?v=2.3 By: Darren http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-326391 Darren Thu, 03 Jul 2008 13:54:54 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-326391 Thank you so much all; I had the <form> tags inside the <table> tags . IE had no problems with it, but Firefox, Opera and Safari refused to recognise the AJAX imported select box. :) Thank you so much all; I had the <form> tags inside the <table> tags . IE had no problems with it, but Firefox, Opera and Safari refused to recognise the AJAX imported select box. :)

]]> By: Charlie Cheng http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-146373 Charlie Cheng Wed, 21 Nov 2007 04:28:48 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-146373 Great article, in firefox, Although, i didn't mess up the tags. But the following may cause the same problem <table> <form ...> ....form field mixed with for layout purpose </form> </table> Move to the following format will make the thing work <form ...> <table> ....form field mixed with for layout purpose </table> </form> Thanks for reminding although i don't exactly problem as you guys. But it does shorten my debugging time. Charlie Great article, in firefox, Although, i didn’t mess up the tags. But the following may cause the same problem

<table>
<form …>
….form field mixed with for layout purpose
</form>
</table>

Move to the following format will make the thing work

<form …>
<table>
….form field mixed with for layout purpose
</table>
</form>

Thanks for reminding although i don’t exactly problem as you guys. But it does shorten my debugging time.

Charlie

]]> By: e http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-90443 e Sat, 11 Aug 2007 15:31:08 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-90443 Also... I'm using a span section around the select field to update it. I'm just giving the span an id and then grabbing onto that with innerHTML. All of this works fine in IE, just not FireFox. Thanks again. Also… I’m using a span section around the select field to update it. I’m just giving the span an id and then grabbing onto that with innerHTML.

All of this works fine in IE, just not FireFox.

Thanks again.

]]> By: e http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-90441 e Sat, 11 Aug 2007 15:26:01 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-90441 In regards to problems with inserting form elements with innerHTML in FireFox, is there some other reading I should find on this site? I ask because it seems that Cedric may have found something more. I'm facing a problem very similar to stocknsurf. I'm not quite sure if it's related to nesting of form tags because there aren't any div layers used on this page. Could the way the form is nested inside of tables cause the same problem? Everything works fine in FireFox until innerHTML is used to update a select field inside the form. Even when the update doesn't cause any changes to the select field (just re-draws it), FireFox stops recognizing the select field. It's as if the select field no longer exists. In regards to problems with inserting form elements with innerHTML in FireFox, is there some other reading I should find on this site? I ask because it seems that Cedric may have found something more.

I’m facing a problem very similar to stocknsurf. I’m not quite sure if it’s related to nesting of form tags because there aren’t any div layers used on this page. Could the way the form is nested inside of tables cause the same problem?

Everything works fine in FireFox until innerHTML is used to update a select field inside the form. Even when the update doesn’t cause any changes to the select field (just re-draws it), FireFox stops recognizing the select field. It’s as if the select field no longer exists.

]]> By: Thanh Le Quoc http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-43957 Thanh Le Quoc Fri, 23 Mar 2007 03:53:34 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-43957 Thanks so much... I also have faced with this problem. Thanks so much…

I also have faced with this problem.

]]> By: Robert Nyman http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-39228 Robert Nyman Wed, 28 Feb 2007 18:52:39 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-39228 Cedric, Glad you found the solution here! :-) Cedric,

Glad you found the solution here! :-)

]]> By: Cedric Colpaert http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-39220 Cedric Colpaert Wed, 28 Feb 2007 17:11:28 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-39220 I had the same problem with the form elements inside innerhtml.. I've spend hours and hours on this.. and there's only one website (this one) where you can find the solution I had the same problem with the form elements inside innerhtml.. I’ve spend hours and hours on this.. and there’s only one website (this one) where you can find the solution

]]> By: Jiv http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-16912 Jiv Wed, 15 Nov 2006 16:51:45 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-16912 In past, I found a way to get rid of the gap IE was putting at the top of the page (equiv. to a ) when inserting the form element like this <code> ... </code> But if you have a look in the DOM source of Firefox you'll see that weird result <code> <strong></strong> ... </code> This can be a possible cause why your variables doesn't get posted! In past, I found a way to get rid of the gap IE was putting at the top of the page (equiv. to a ) when inserting the form element like this

...


But if you have a look in the DOM source of Firefox you’ll see that weird result

…


This can be a possible cause why your variables doesn’t get posted!

]]> By: zhenya http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-14086 zhenya Mon, 30 Oct 2006 15:51:09 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-14086 Tref, I also want to thank you. I've spent 4 hours today trying to solve same problem and after I read your message I only had to make cut-past and it worked! Tref, I also want to thank you. I’ve spent 4 hours today trying to solve same problem and after I read your message I only had to make cut-past and it worked!

]]> By: jp http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-12590 jp Mon, 16 Oct 2006 15:47:42 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-12590 Thank you so much tref, that was the problem for me too. I thought it would never be solved... Thank you so much tref, that was the problem for me too. I thought it would never be solved…

]]> By: Robert Nyman http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-11261 Robert Nyman Tue, 03 Oct 2006 06:38:54 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-11261 Tref, Thanks for the info. Tref,

Thanks for the info.

]]> By: Tref http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-11259 Tref Tue, 03 Oct 2006 06:01:20 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-11259 Forgive me.. my explanation was back to front.. should read <blockquote> The answer was in the nesting of the form fields. The opening form tag was above the “page”, whereas the closing tag was between the closing of the "main" and the “page” div. </blockquote> Forgive me.. my explanation was back to front.. should read

The answer was in the nesting of the form fields. The opening form tag was above the “page”, whereas the closing tag was between the closing of the “main” and the “page” div.

]]> By: Tref http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-11258 Tref Tue, 03 Oct 2006 05:58:59 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-11258 stocknsurf, I've just had to debug a similar scenario so in case you haven't located the answer here's what I found out. Firefox may not accept your ajax imported form elements if the opening and closing form tags are not nested correctly. For example we had a page that had the following structure. <code> < body> < form name="form1" method="post" action="gohere.jsp" > < div id="page"> < div id="main" > ... main content with form elements went here.. ... some dynamic form elements were inserted using ajax calls </div > </form > </div > </body > </code> We were inserting some form fields into the form via an ajax call but in firefox they were not showing up. We could access them by document.getElementById but document.form1.foo was coming up "undefined" The answer was in the nesting of the form fields. The opening tag was between the "page" and "main" divs, whereas the closing tag was after the closing "page" div. Hope that helps your situation cheers stocknsurf, I’ve just had to debug a similar scenario so in case you haven’t located the answer here’s what I found out.

Firefox may not accept your AJAX imported form elements if the opening and closing form tags are not nested correctly.

For example we had a page that had the following structure.

< body>

< form name="form1" method="post" action="gohere.jsp" >

< div id="page">

< div id="main" >

... main content with form elements went here..

... some dynamic form elements were inserted using AJAX calls

</div >

</form >

</div >
</body >

We were inserting some form fields into the form via an AJAX call but in firefox they were not showing up. We could access them by document.getElementById but document.form1.foo was coming up “undefined”

The answer was in the nesting of the form fields. The opening tag was between the “page” and “main” divs, whereas the closing tag was after the closing “page” div.

Hope that helps your situation

cheers

]]> By: Robert Nyman http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-7802 Robert Nyman Tue, 29 Aug 2006 10:11:20 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-7802 stocknsurf, I haven't encountered this myself, but my guess is that Firefox looks at form fields in a different way. This might be a scenario where you will have to resort to DOM methods like <code>createElement</code>, <code>appendChild</code> etc to make it work. Good luck! stocknsurf,

I haven’t encountered this myself, but my guess is that Firefox looks at form fields in a different way. This might be a scenario where you will have to resort to DOM methods like createElement, appendChild etc to make it work.

Good luck!

]]> By: stocknsurf http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-7799 stocknsurf Tue, 29 Aug 2006 10:05:15 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-7799 Hi I am facing a problem with innerhtml in firefox. Basically this is the issue: I have a divid content which is changed dynamically using innerHTML. This divid is inside a form and as a part of the dynamic content I am adding new form fields dynamically using innerHTML (based on user actions). But the problem is when the form is submitted from firefox, these new form fields don't get passed on to the server side at all. Only the static fields that already existed get passed on. This is the problem I face only with firefox. On IE the new form fields added using innerHTML gets passed on to the server side successfully. I am splitting my hair over this problem with firefox. Has anyone faced the same issue? How do I solve this? Thanks Hi I am facing a problem with innerhtml in firefox.

Basically this is the issue:

I have a divid content which is changed dynamically using innerHTML. This divid is inside a form and as a part of the dynamic content I am adding new form fields dynamically using innerHTML (based on user actions).

But the problem is when the form is submitted from firefox, these new form fields don’t get passed on to the server side at all. Only the static fields that already existed get passed on.

This is the problem I face only with firefox. On IE the new form fields added using innerHTML gets passed on to the server side successfully.

I am splitting my hair over this problem with firefox. Has anyone faced the same issue? How do I solve this?

Thanks

]]> By: Robert Nyman http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4392 Robert Nyman Thu, 27 Apr 2006 08:33:46 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4392 Asbjørn, I'm happy to hear that you share our opinions! Asbjørn,

I’m happy to hear that you share our opinions!

]]> By: Asbjørn Ulsberg http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4383 Asbjørn Ulsberg Wed, 26 Apr 2006 22:11:51 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4383 Standardising <code>innerHTML</code> is a Good Thing. No doubt. It's a de facto standard and we're all better off with it being a real standard. Let's just hope we can get it better specified, perhaps with some error handling (when the document is in standard mode and invalid markup is inserted, an exception could occur for example) and maybe even a better name (<code>innerMarkup</code> and <code>outerMarkup</code> would be nice). Standardising innerHTML is a Good Thing. No doubt. It’s a de facto standard and we’re all better off with it being a real standard. Let’s just hope we can get it better specified, perhaps with some error handling (when the document is in standard mode and invalid markup is inserted, an exception could occur for example) and maybe even a better name (innerMarkup and outerMarkup would be nice).

]]> By: Robert Nyman http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4234 Robert Nyman Sun, 23 Apr 2006 19:44:43 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4234 Aristotle, <blockquote>So you have a situation where there’s a pragmatic but bug-prone API, and a precise but indescribably painful one.</blockquote> I think that sums it up pretty well. But between those two, I'd go for the pragmatic one, given the current situation. Not sure if <a href="http://en.wikipedia.org/wiki/E4X" rel="nofollow">E4X</a> is the solution to all, but it definitely sounds like an interesting option! Aristotle,

So you have a situation where there’s a pragmatic but bug-prone API, and a precise but indescribably painful one.

I think that sums it up pretty well. But between those two, I’d go for the pragmatic one, given the current situation.

Not sure if E4X is the solution to all, but it definitely sounds like an interesting option!

]]> By: Aristotle Pagaltzis http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4225 Aristotle Pagaltzis Sun, 23 Apr 2006 09:33:46 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4225 DOM blows, any way you turn it. It’s clumsy and extremely verbose. Only things like DOM Builder make it tolerable. However, innerHTML blows far worse for exposing you to the vagaries of multiple layers and dealing with escaping. So you have a situation where there’s a pragmatic but bug-prone API, and a precise but indescribably painful one. The answer is clear: we need cross-browser E4X and <em>we need it now</em>. DOM blows, any way you turn it. It’s clumsy and extremely verbose. Only things like DOM Builder make it tolerable. However, innerHTML blows far worse for exposing you to the vagaries of multiple layers and dealing with escaping.

So you have a situation where there’s a pragmatic but bug-prone API, and a precise but indescribably painful one.

The answer is clear: we need cross-browser E4X and we need it now.

]]> By: Laurens Holst http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4200 Laurens Holst Fri, 21 Apr 2006 22:19:53 +0000 http://www.robertnyman.com/2006/04/20/we-all-love-innerhtml/#comment-4200 Indeed :). Indeed :).

]]>