WHATWG Weekly: Search Provider APIs
WHATWG Weekly will go on vacation for three months three weeks from now. However, you can stop that by joining IRC and offering to write it instead. You will be given at least one Internet for each post.
Shorts from the WHATWG mailing list
David Flanagan pointed out that various event handlers are on the
HTMLElement interface rather than
HTMLMediaElement even though the events are non-bubbling and dispatched solely on
HTMLMediaElement. Philip Jägenstedt explained that it makes them more straightforward to implement. Why they are also on
Window was not explained.
David Levin suggested we standardize APIs for adding search providers. A way for a site the user is visiting to find out whether it is the default search provider and a way to add itself as search provider. The APIs he suggests we converge on are proprietary APIs from Internet Explorer.
As part of the real-time web APIs the HTML specification defines a
StreamRecorder interface so authors can obtain a
File out of some streaming media data. Ian Hickson indicated this is still very experimental. We are basically looking for feedback from implementors and authors, as well as standardization of the various protocols and formats, before proceeding with the APIs.
Michael Nordman said he plans on changing Chrome to allow cross-origin caching of secure resources for the application cache feature. The idea is to respect
Cache-Control: no-store giving the cross-origin resources control over the situation.
Philip Jägenstedt reported he nuked
Jukka K. Korpela provided feedback on the new controls. I remember reading his Guidelines on
alt texts in
img elements back in the day and realizing that markup is fricking complex. Pretty cool that he is now reviewing our work.
At the W3C
Over the past week or so I updated DOM Core (formerly Web DOM Core) to include events.
When more popular sites adopted the
#! URL pattern advocacy articles were written, e.g: Breaking the Web with hash-bangs. The WHATWG saw this coming which is why we came up with the
history.pushState() API some time ago. It allows resources to manipulate the path of their URL.