Thank you! I had only tried this approach because it was there in the examples! : ( From what I have seen/read using the innerHtml for creating the DOM is much faster than actually creating widgets etc etc in terms of rendering. So is CellTable the alternative to doing what i did? Or is there some other way too?
On Jan 13, 1:15 am, Thomas Broyer <[email protected]> wrote: > If you get the *inner* HTML of a table, you'll only take the tbody and its > children which, when inserted into a div with innerHTML (i.e. parsed as if > there were in that div, instead of a table) strips the table elements > (tbody, tr, td). > What you'd need is a getOuterHTML which unfortunately cannot be made > crossbrowser, so you'll have to insert the table into another element (such > as a div) and get that element's innerHTML. > Or you could append the table element to another element instead fo > serializing it to HTML to parse it back to a DOM right here after. > > ...or you could use a CellTable instead of building the table's HTML by hand > (your code is vulnerable to script injection) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
