[whatwg] The <keygen> element
jonas at sicking.cc
Thu Jun 4 01:33:44 PDT 2009
On Wed, Jun 3, 2009 at 3:31 PM, Ian Hickson <ian at hixie.ch> wrote:
>> Which is more likely to be adopted as a cross browser standard? A new
> It would presumably depend on how it is to be used. If it's for form
> submission, then an element would make more sense. If it's for
> applications, then an API would be better.
As a browser developer I'd say that the likeliness something is
implemented depends heavily on how useful it is perceived to be, and
somewhat on how hard it is to implement.
If a feature doesn't seem very useful, I wouldn't advocate adding it
no matter how easy it is to implement. On the other hand, if a feature
is hard enough to implement that we can implement two other features,
that add up to more usefulness, then implementing those two features
seem to serve the web more.
All of this is very simplified of course, and highly subjective.
But neither a new element or a new JS object is hard to implement in
and of itself. So use the best solution for the task, that's the most
likely to yield a useful feature.
More information about the whatwg