[Webkit-unassigned] [Bug 73039] [Web Intents] Flagged-off implementation of an intent tag for registration.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=73039





--- Comment #16 from Greg Billock <gbillock at google.com>  2011-12-01 11:48:36 PST ---
(In reply to comment #15)
> It's not clear to me whether creating a new HTML tag is the right thing to do.  Generally, that sort of thing is pretty expensive.  Is there an archive of a mailing list discussion (e.g., in the W3C or the WhatWG) I can read to get a sense of the pros and cons?

I hear you. While we like the accessibility and discoverability of the tag, it isn't clear to everyone it is worth it. A bigger concern than the impact on the HTML spec, so far, has been over what happens if the tag contents change, or even worse, if it disappears. We've had discussions about this reported on https://groups.google.com/group/web-intents.

The W3C task force group (public-web-intents; http://lists.w3.org/Archives/Public/public-web-intents/) just started up, but we will be discussing these issues in more depth there. Our prototype code also has ways to register intents in the manifest of a web app. So this tag isn't the only discovery/registration mechanism proposed.

Since this is a prototype implementation, all the code for this tag is flagged off. People creating custom browser builds or enabling the tag with browser flags is the most we except to do until these issues get resolved. If we decide to not pursue the tag, all this tag code will be backed out again. The only place this isn't the case, as I've noted, is with the "disposition" attribute. I could add a way for conditional emission of attributes. I don't think there is one now the way there is with tag names. Do you think that is desirable? Or should I change it to x-webkit-intent?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.