Awesome, thanks!
/ Jonas
On Tue, Feb 21, 2012 at 5:18 AM, Adam Barth w...@adambarth.com wrote:
I've updated http://wiki.whatwg.org/wiki/Crypto to have
getRandomValues return the array.
Adam
On Mon, Feb 20, 2012 at 2:51 PM, Jonas Sicking jo...@sicking.cc wrote:
Hi All,
For reference,
Þann mið 15.feb 2012 23:39, skrifaði James Hawkins:
* If |scheme| is specified, |action| *should* (must?) be ignored.
Why would you forbid distinguishing between actions on URIs? Postal and
retrieval of mail, for example, are quite distinct actions. As are
modification and retrieval of
Thanks for your feedback, Bjartur.
On Tue, Feb 21, 2012 at 9:30 AM, Bjartur Thorlacius svartma...@gmail.comwrote:
Þann mið 15.feb 2012 23:39, skrifaði James Hawkins:
* If |scheme| is specified, |action| *should* (must?) be ignored.
Why would you forbid distinguishing between actions on
Þann þri 21.feb 2012 18:44, skrifaði James Hawkins:
I'm not sure if the proposal was explicit enough, but for the RPH-esque
functionality in Web Intents, we activate WI in the same circumstances
RPH is activated, which is when links are activated in a page. Can you
elucidate how the scenarios
On Tue, Feb 21, 2012 at 11:31 AM, Bjartur Thorlacius
svartma...@gmail.com wrote:
Þann þri 21.feb 2012 18:44, skrifaði James Hawkins:
I'm not sure if the proposal was explicit enough, but for the RPH-esque
functionality in Web Intents, we activate WI in the same circumstances
RPH is activated,
Þann þri 21.feb 2012 19:41, skrifaði James Hawkins:
Is this use case not fully handled by the UA specifying the
appropriate action when building the intent, e.g., the user
right-clicks on an image in a page and the UA constructs context menu
items for edit/share/etc. action?
Not if the image is
On Tue, 13 Sep 2011, Michael Gratton wrote:
HTML5 does not provide a means of submitting form content that is
otherwise rendered as normal text, i.e. not as a form control. The use
cases for this are the same as for the output element, but when it is
also desirable for the result of a
Hi,
We just published a joint proposal for adding Encrypted Media to
HTMLMediaElement on the W3C website:
http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html;
announcement:
http://lists.w3.org/Archives/Public/public-html/2012Feb/0273.html. To avoid
forking the
I propose that source add a quality, bitrate, or filesize attribute to allow
the UA to decide between multiple streams by choosing the maximum quality file
that it can download within a reasonable amount of time (e.g. it will download
faster than it will play) or based on a user preference
On Sat, 24 Sep 2011, Kaustubh Atrawalkar wrote:
On 24-Sep-2011, at 12:24 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 23 Sep 2011, Kaustubh Atrawalkar wrote:
If the form has submit button with display property as none, will that
form should be implicitly submitted on pressing enter key?
On 2/21/12 7:35 PM, Ian Hickson wrote:
On Sun, 25 Sep 2011, Boris Zbarsky wrote:
Not doing that last is actually a requirement for web compat, last I
looked at this.
Do you have any links to pages that break if a form with more than one
text field supports implicit submission?
Not offhand.
On Tue, Feb 21, 2012 at 6:35 PM, Ian Hickson i...@hixie.ch wrote:
(It also explicitly says that if implicit submit is supported but
there's no submit button in the form, the implicit submit must still
happen. That doesn't sound like it could be followed, since lots of
pages are probably
On Tue, Feb 21, 2012 at 5:36 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/21/12 7:35 PM, Ian Hickson wrote:
On Sun, 25 Sep 2011, Boris Zbarsky wrote:
Not doing that last is actually a requirement for web compat, last I
looked at this.
Do you have any links to pages that break if a form
On 2/21/12 10:47 PM, Dimitri Glazkov wrote:
I made WebKit match this behavior a couple of years ago:
https://bugs.webkit.org/show_bug.cgi?id=9756
Ah, interesting. Some of the links in that bug indicate that people are
in fact depending on this behavior
-Boris
On Sat, 8 Oct 2011, Kaustubh Atrawalkar wrote:
In a form element, If a form input element has a focus and its then made
hidden using style property display:none the focus still remains on the
hidden element. According to specs (
On Mon, 26 Sep 2011, Ojan Vafai wrote:
*8.3.2 Focus management*
An element is *focusable* if the user agent's default behavior allows it to
be focusable or if the element is specially focusable, but only if the
element is either being rendered or is a descendant of a canvas element that
16 matches
Mail list logo
