> The other way to skin this cat, by the way, is to implement the > seamless attribute on iframes. That gives you a similar sort of > design using the @sandbox attribute and solves many of your above > concerns, e.g. by creating a new namespace for @ids. Maybe we should > try that first or in parallel?
I would think that in practice, IFRAMEs would, at least psychologically, be significantly less useful to web app developers. This is due to the fact that frames are conceptually more difficult to properly position and size to accommodate any dynamically inserted text; are more cumbersome to pre-populate with data on server-side (extra HTTP roundtrips or opaque data: URLs). Also, are renderer implementations actually ready to handle hundreds of seamless IFRAMEs on a page with the performance footprint not exceeding that of spans and divs? /mz _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
