Just for clarity, setting innerhtml as property is *not* a JavaScript error and is therefore not shown as exception within Firebug's (or any other devtools') console. To find errors like this one step debugging your code may come in very handy. I.e. when you step over the statement where you set the innerhtml property and you see that the contents are not added to the page as expected, it should be easy to see why that's the case.
Sebastian On Friday, February 19, 2016 at 7:00:08 AM UTC+1, CharlesEF wrote: > > Ok, thanks for the information. > > On Thursday, February 18, 2016 at 4:27:35 PM UTC-6, alfonsoml wrote: >> >> None of the debuggers will help you if you try to write to a non-existing >> property because the browser will automatically create that property. >> If you inspect that element you'll see that it included both the >> innerHTML as well as you custom innerhtml properties >> >> >> >> On Thursday, February 18, 2016 at 7:10:48 PM UTC+1, CharlesEF wrote: >>> >>> Hi All, >>> >>> I ran into this problem, I made a case mistake in the javascript >>> property 'innerHTML'. I used 'innerhtml; instead and when my results >>> didn't display I turned to Firebug for help. I find that Firebug was of no >>> help this time. No error was reported. >>> >>> Is there a configuration option I overlooked? Or, is Firebug not able >>> to catch these kinds of errors? >>> >>> Thanks for any help, >>> >>> CharlesEF >>> >> -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/e1f142f2-cabc-456b-b3f2-43e49a51df71%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
