Summary: Currently we have <iframe mozbrowser> which has a bunch additional functionality than simple <iframe> and is a top level browsing context by itself. Having <webview> avoids overloading <iframe> and provides clarity. We also think this is the right direction towards the standardization of the browser-element.
For the story of <iframe mozbrowser> see https://hacks.mozilla.org/2014/08/building-the-firefox-browser-for-firefox-os/ Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=738172 Link to standard: Currently no formal standard. Ben Francis has created a draft which largely resembles the current mozbrowser API. Google and Microsoft both have their <webview> implementation similar to this proposal. http://benfrancis.github.io/webview/ https://developer.mozilla.org/en-US/docs/Web/API/Using_the_Browser_API https://developer.chrome.com/apps/tags/webview http://msdn.microsoft.com/en-gb/library/windows/apps/dn301831.aspx Platform coverage: Initially on Firefox OS Estimated or target release: Firefox OS 2.4 Preference behind which this will be implemented: It will be behind a pref dom.enable_webview. The html5 parser should be taught to treat the tag as HTMLUnknownElement when preffed off.
signature.asc
Description: PGP signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
