On Wed, Jan 14, 2015 at 2:58 PM, Janusz Majnert wrote:
> On 14.01.2015 14:01, Anne van Kesteren wrote:
>>
>> Andrea just landed the last patch for the BroadcastChannel API:
>>
>>https://bugzilla.mozilla.org/show_bug.cgi?id=966439
>>
>> https://html.spec.whatwg.org/multipage/comms.html#broadcas
> On Wed, Jul 31, 2013 at 9:15 PM, Ian Hickson wrote:
>> On Wed, 31 Jul 2013, Laurent Perez wrote:
>> >
>> > Is there work going on on a Splash screen specification ?
>>
>> What's the use case?
>>
>> Generally speaking, Web pages load incrementally, so by the time you've
>> downloaded an image, yo
Scott González wrote:
On Tuesday, May 8, 2012, Doug Turner wrote:
You don't. This API doesn't have device detection. Don't assume that
onXXX means that the UA supports an event.
I thought this was the preferred way to check. I seem to recall a
discussion about this and agreement that this
During some experimentation today I wanted to establish a
cross-document messaging channel for when a user submits a form with a
target of _blank (or _someframe). I couldn't find any native way to do
this when target == _blank so I had to produce my own workaround [1].
In the course of doing this
Olli Pettay wrote:
On 07/06/2011 07:51 AM, Robert O'Callahan wrote:
I don't think browsers need to prompt for registerProtocolHandler.
Instead,
I would simply allow any site to register as a protocol handler for
almost
anything, and remember all such registration
So all the ad sites (which are
Rich Tibbett wrote:
Peter Kasting wrote:
On Fri, Jul 1, 2011 at 1:59 PM, Ojan Vafai wrote:
Do any browser vendors agree with this or have objections?
From my work on the Chrome UI side of this, I would very much like to
see
something like isRegistered(). This would allow sites to
Peter Kasting wrote:
On Fri, Jul 1, 2011 at 1:59 PM, Ojan Vafai wrote:
Do any browser vendors agree with this or have objections?
From my work on the Chrome UI side of this, I would very much like to see
something like isRegistered(). This would allow sites to conditionalize
requests for
Biju wrote:
What I want from browser vendors is make
navigator.geolocation.getCurrentPosition
and navigator.geolocation.watchPosition ONLY callable from a CLICK event.
I thought we all learned lesson from window.open popups
window.open is still entirely underspecified in standards when it comes
Hi,
We noticed a number of deficiencies with the way a developer can
obtain a GeneratedStream object. Hopefully I can explain those
succinctly below.
A callback-based model fires a single success event. An events-based
API allows for ongoing intermediate readyState changes to be fired at
web page
Andrei Popescu wrote:
Hi Anne,
On Wed, Feb 16, 2011 at 12:36 PM, Anne van Kesteren wrote:
On Tue, 15 Feb 2011 17:48:24 +0100, Leandro Graciá Gil
wrote:
All feedback will be greatly appreciated.
This is just a thought. Instead of acquiring a Stream object asynchronously
there always is one
Tab Atkins Jr. wrote:
The file input gained the @accept attribute a little while ago, to
indicate what type of file should be accepted. It has three special
values, "image/*", "video/*", and "audio/*".
I believe one intent of these special values is that browsers may
offer the user the ability
Jens Müller wrote:
Hi,
now that device orientation, geolocation, camera etc. have been spec'ed:
Is there any intent to provide an API for pressure sensors?
This might well be the next hip feature in smartphones ...
Oh, and while we are at it: Humidity probably belongs to the same group.
Cou
Henri Sivonen wrote:
In HTML5, a URL (or a set of URLs) point at what you want the
user-agent to display. From the spec's point of view, you can insert
any protocol (that can be described by a URL) in there. You'll need it
to be supported by your user-agent, of course.
In practice, live streami
13 matches
Mail list logo
