On Mon, Dec 31, 2012 at 3:58 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> On 12/30/12 11:14 PM, Bobby Holley wrote: > >> 1) How do we want this to work going forward for chrome touching content? >> >> |obj instanceof Node| should return true. >> >> 2) How do we want this to work going forward for web pages touching >>> other >>> web pages? >>> >> >> |obj instanceof Node| should return false until the standards community >> decides something to the contrary and specs it. >> > > OK. What do we do with b2g? I'm not quite sure whether the code in there > I see using instanceof is running in "chrome"; most of b2g doesn't do > that.... Well, if we're talking about JS-implemented WebAPIs, then that stuff should be running as chrome, potentially in the content process (unless I'm mistaken - I'm still a bit behind on all the b2g architecture). If we're talking about web apps, then they're supposed to be regular old web content, and we shouldn't do anything special for them in Gecko. Doing so undermines our position that these apps are open and portable. If we think it would significantly improve the web as a platform, I'm certainly down to push for it (in the front seat) with other vendors. But I'd think the arguments should be based on improving the HTML5 developer experience, rather than improving the B2G developer experience. Theoretically, there isn't supposed to be much of a difference. ;-) bholley _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
