On Feb 7, 1:02 am, Miller Medeiros <[email protected]> wrote: > > my app should also run inside a WebView
In any case. Mobile Safari is a webview too. > - it will live inside an Ad on a > native application, something like an iAd that should also accessible using > the browser - the bug isn't only related with PhoneGap... How do you know ? Have you seen the test case ? Do you know what did she do to get it ? Why do you say that it's not only related to Phonegap, when she got "phonegap" in the innerhtml ? You can't tell until you see the code. > anyone experienced any bugs with `document.createElement` and > `document.createTextNode`? I'm really considering in not using innerHTML at > all for this kind of project in the future since the benefits are > questionable... I don't care even the slightest what you use (no offense meant). But one thing I do care and I know for sure: you should only be afraid of .innerHTML in IEs, not in Safari nor in Chrome nor in Opera nor in FireFox. > a good part of the flash community migrated from timeline animations mixed > with code to pure scripting/OOP a few years ago to avoid similar issues, > anyone think that JS will take the same path for specific kinds of projects? > (maybe the same kind of projects that flash is used for) - I'm starting to > think that it will.. Perhaps that's true. But keep in mind that the parser that .innerHTML uses is the same parser that builds the page from the .html. In other words, if you can't trust it, you can't trust anything in the page. > thanks for all the answers so far, I didn't knew about some of the bugs > (never tried to use innerHTML outside the body tag). Nor tried to insert another <head> in the <body>, right ? -- 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]
