|Summary:||Make Webkit process HbbTV and CE-HTML documents as XHTML|
|Product:||WebKit||Reporter:||Mark Toller <mark.toller>|
|Severity:||Normal||CC:||abarth, eoin.shanaghy, mario.bensi, mtheriault, sangwhan|
|Version:||528+ (Nightly build)|
Description Mark Toller 2012-10-11 06:29:50 PDT
The aim of this is purely to make Webkit understand the CE-HTML and HbbTV mime types in order to treat the document as XHTML (which they are) and attempt to render the documents rather than prompt the user to download the file. CE-HTML and HbbTV documents are XHTML documents which are served with mime types of "application/ce-html+xml" or "application/vnd.hbbtv.xhtml+xml". Additionally, HbbTV documents may contain the following doctype declarations: <!DOCTYPE html PUBLIC "-//HbbTV//1.1.1//EN" "http://www.hbbtv.org/dtd/HbbTV-1.1.1.dtd"> <!DOCTYPE html PUBLIC "-//HbbTV//1.2.1//EN" "http://www.hbbtv.org/dtd/HbbTV-1.2.1.dtd"> Most CE-HTML and HbbTV application main pages can be rendered by Webkit correctly without modification, and many HbbTV applications will run as far as possible without the TV specific functionality (depending on how well the application is authored). There is no benefit in prompting the user to 'save' or 'open' such files locally, whereas if Webkit renders such applications, it will provide HbbTV application authors with additional browsers that can be used to verify basic functionality of their applications. This in turn may help guide HbbTV authors to use more 'core' W3C/HTML5 and less CE-HTML specific code where possible. The changes to Webkit to support this are minimal and obvious, and should not cause any maintenance overhead at all (in fact, support for other such documents exists in the same areas, such as the WML mime type and doctype).
Comment 2 Adam Barth 2012-10-11 09:15:22 PDT
Should this be behind an ENABLE macro? I don't see these media types registered at <http://www.iana.org/assignments/media-types/application/index.html>. Not every media type needs to be registered, but it's generally better if they are. If these documents are XHTML, why not just use the XHTML media type?