On Feb 7, 2:18 am, Diego Perini <[email protected]> wrote: > On Mon, Feb 7, 2011 at 1:17 AM, Jorge <[email protected]> wrote: > > On Feb 7, 12:46 am, Diego Perini <[email protected]> wrote: > > >> Those were the bugs I found advice for here: > > >> http://webbugtrack.blogspot.com/2009/08/bug-179-innerhtml-love-outsid... > > > Let's forget that... it's not serious. Not even a test case. > > >> And a quick search for .innerHTML on Webkit bug list revealed these > >> (among others): > > >> https://bugs.webkit.org/show_bug.cgi?id=43953 > >> "innerHTML Delete HEAD and BODY tags" > > > Yep. Have you read it ? He's inserting a <head> into a <div> into the > > <body>, and webkit refuses to do so. Well, I don't know what could be > > the use, but at the very best, if a second <head> in the <body> does > > make any sense (does it?), you should agree that it's a very very > > corner case, completely unusual. > > > Are you trying to ditch webkit's innerHTML for refusing to insert a > > second <head> into the <body>, REALLY ? > > >> https://bugs.webkit.org/show_bug.cgi?id=45188 > >> "Setting innerHTML to a video element does not respect autoplay" > > > These are HTML5 tags, new things, and the APIs are in perpetual flux, > > currently. Again, that's no reason to ditch innerHTML. And, I'd bet > > that a setAttribute would have failed as well. > > > Surely, if you dig enough in the bugtrackers, you're going to find > > bugs in some DOM methods too, are you going to "advice" against using > > them too ? > > >> I haven't tested all these bugs myself on all platforms and Webkit > >> versions but I must believe to those, at least those on Webkit bug > >> tracker. > > > You these are the "known problems" you were referring to ? > > -- > > Jorge. > > I for myself are ditching ".innerHTML" because it doesn't behave the > same across browsers and basically because alternatives exists. > > It all depends for what the poster is going to use it. I am making > sure to pass all the info I have. The OP is going to pick what works > for him. > > I am just giving my advice to the OP standing the history of my > observations and reporting about any bug that I know about the matter > talked about. You are free not to follow the advice if you see no > value in it. > > I am not here to sell something, nor against some specific browser and > I am happy if Safari/Chrome have the best ".innerHTML" implementation. > > That doesn't change what has been said.
You seem to believe that all other browsers are as crappy as IEs, when they're not :-) -- Jorge. -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
