On Thu, Jun 18, 2015, at 19:19, Edward O'Connor wrote:
Maciej replied:
I find this use case pretty compelling. There’s no reasonable set of
processing steps that could get you salmon pink for use as a
background, but black for use as a foreground. I think this is
compelling evidence that
On Tue, Oct 28, 2014 at 6:33 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 15 Feb 2014, Brett Zamir wrote:
The desktop PC thankfully evolved into allowing third-party software
which could create and edit files shareable by other third-party
software which would have the same rights to do
On Wed, Oct 8, 2014 at 9:40 AM, Silvia Pfeiffer silviapfeiff...@gmail.com
wrote:
Indeed, a Web Bluetooth API would be a great start!
Also, we are writing standards here, so standardizing the
communication of the data between the devices and UAs would be useful.
Both would probably fall
On Wed, Oct 8, 2014 at 9:51 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
The question is whether it's not natural to assume that *if the promise
fulfills*, that means they got permission. This allows them to do things
like using Promise.all() to join multiple permission requests together and
On Wed, Oct 8, 2014 at 5:59 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Oct 8, 2014 at 1:31 AM, Tobie Langel tobie.lan...@gmail.com
wrote:
On Wed, Oct 8, 2014 at 9:51 AM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
The question is whether it's not natural to assume
On Wed, Oct 1, 2014 at 5:59 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
I've never heard this opinion explicitly expressed, and it has never
shown up in any API reviews of promise-using specs. It's directly
contrary to the way that existing non-promise async APIs are
constructed, and I
On Wed, Oct 1, 2014 at 7:22 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Note that Python, for example, throws errors on dict keys not being
found (unless you specifically tell it a sentinel value to return
instead). Do you think that's terrible?
Sure. But JS doesn't.
On Wed, Oct 1, 2014 at 11:43 PM, Anne van Kesteren ann...@annevk.nl wrote:
Given async/await the only reasonable thing to do seems to me
to model them after functions and only use rejection for something
exceptional, but with the level of disagreement this has created in
several different
On Jun 26, 2014, at 21:20, Marcos Caceres w...@marcosc.com wrote:
On June 26, 2014 at 1:58:17 PM, Tab Atkins Jr. (jackalm...@gmail.com) wrote:
Here's a first crack at a better spec:
Moved your text here:
https://github.com/whatwg/meta-brand-color
Could we change the name to something a tad
On Wed, Jun 18, 2014 at 12:08 PM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Jun 16, 2014 at 6:57 PM, Jussi Kalliokoski
jussi.kallioko...@gmail.com wrote:
var doesFetchSupportJson = function () {
return fetch(data:application/json;base64,e30=).then(function
(response) {
On May 25, 2014, at 8:59, Michael Heuberger
michael.heuber...@binarykitchen.com wrote:
Thanks Silvia for your comment but I think we turn in circles.
I know you mean it well but this is not the case as I mentioned it over
and over again in my previous emails.
Let me repeat, the whole SPA of
Hi again,
On May 25, 2014, at 9:35, Michael Heuberger
michael.heuber...@binarykitchen.com wrote:
* It is a redundancy. The browser already knows the status code, just
not JavaScript.
That argument can equally well be used the other way round: it's a
redundancy to expose in JS something that
On May 4, 2014, at 7:45, Rik Cabanier caban...@gmail.com wrote:
On Sat, May 3, 2014 at 10:32 PM, Eli Grey m...@eligrey.com wrote:
The proposal specifically states using logical cores, which handles
all of the CPUs you mentioned properly.
Intel CPUs with hyperthreading enabled report logical
On Thursday, October 31, 2013 at 12:42 PM, Anne van Kesteren wrote:
Should really have a way to file a bug on all browsers whenever
something like this comes up...
Yes please.
--tobie
On Thursday, October 31, 2013 at 4:27 PM, Ms2ger wrote:
On 10/31/2013 04:13 PM, Boris Zbarsky wrote:
In particular, I don't believe browser vendors
typically run W3C test suites en masse regularly,
Just going to note here that James Graham is, in fact, working on doing
that for
On Thursday, October 31, 2013 at 5:07 PM, Bjoern Hoehrmann wrote:
* Boris Zbarsky wrote:
If the goal is to get browsers to implement, how is it more valuable?
Browser vendors ignore W3C test suites to an even greater extent than
they ignore bug reports. In particular, I don't believe
On Thursday, October 24, 2013 at 11:05 AM, Anne van Kesteren wrote:
On Thu, Oct 24, 2013 at 2:19 AM, Nikhil Marathe nsm.nik...@gmail.com
(mailto:nsm.nik...@gmail.com) wrote:
The easiest solution for implementors and authors is to make the
requestPermission() call in a HTML page before
On Wednesday, September 18, 2013 at 5:27 PM, Glenn Maynard wrote:
On Wed, Sep 18, 2013 at 7:18 AM, Niels Keurentjes
niels.keurent...@omines.com (mailto:niels.keurent...@omines.com) wrote:
The spec should only concern itself with exposing functionality. Practical
considerations such as
On Tuesday, September 10, 2013 at 11:22 PM, Ian Hickson wrote:
On Sat, 13 Jul 2013, Tobie Langel wrote:
It is not uncommon for mobile experiences to rely on the accelerometer
as an input mechanism, for example to control page scrolling (e.g.
Instapaper) or for gameplay.
In such cases
On Tuesday, July 16, 2013 at 7:53 PM, Ian Hickson wrote:
Can't you do window.isSameOrigin by just trying to access
window.location.href and seeing if you get an exception?
Unfortunately not, because of the previously mentioned WebKit bug which logs an
error message but doesn't throw (so
On Friday, July 12, 2013 at 9:45 PM, Ian Hickson wrote:
On Thu, 18 Apr 2013, David Bruant wrote:
Currently working on a web project where tablet support (iPad
especially) is important, I'm facing a need which apparently the
platform doesn't support. I would need to lock the screen in
On Friday, March 8, 2013 at 10:44 AM, Robin Berjon wrote:
On 07/03/2013 23:34 , Tobie Langel wrote:
Wouldn't some form of event-based API be more indicated? E.g.:
var parser = JSON.parser();
parser.parse(src);
parser.onparse = function(e) { doSomething(e.data); };
I'm not sure how
I'd like to hear about the use cases a bit more.
Generally, structured data gets bulky because it contains more items, not
because items get bigger.
In which case, isn't part of the solution to paginate your data, and parse
those pages separately?
Even if an async API for JSON existed,
On Sat, Dec 22, 2012 at 2:57 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Dec 22, 2012 at 2:43 PM, Cameron McCormack c...@mcc.id.au wrote:
On 23/12/12 12:40 AM, Anne van Kesteren wrote:
I guess dashList is somewhat simpler, but I think it would be nice if
it still did type
On Tue, Dec 18, 2012 at 7:09 PM, Rick Waldron waldron.r...@gmail.comwrote:
Has there been any work or discussion with regard to standardizing the
Console object?
FWIW, the Browser Testing and Tools Working Group is chartered to work on
it, but I don't know whether there's actual work
On Dec 13, 2012, at 8:42 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 13 Dec 2012, Stan wrote:
The reasoning for this API is the need to uniquely identify every device
in many web-applications.
Why do you need to identify the device? What about if the user uses the
same browser profile on
On Tue, Nov 20, 2012 at 6:47 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 26 Mar 2012, Adam Barth wrote:
For nested browsing contexts, expose the origin of the parent browsing
context via location.parentOrigin. (For non-nested browsing context,
the property would null.)
This ended up
On Mon, Sep 24, 2012 at 10:58 AM, Anne van Kesteren ann...@annevk.nl wrote:
The kind of predictability we have for the HTML parser, I want to have for the
URL parser as well.
Yes, please!!
--tobie
On Sep 11, 2012, at 7:09, Cameron McCormack c...@mcc.id.au wrote:
Tobie Langel:
No. It sounds like I should be fast asleep instead of making a fool of
myself and wasting everybody's time.
It is however the kind of thing that Tab wants to do for CSS (have a
window.CSS object that is like
On Tue, Sep 11, 2012 at 10:34 AM, Simon Pieters sim...@opera.com wrote:
On Tue, 11 Sep 2012 00:14:25 +0200, Glenn Maynard gl...@zewt.org wrote:
If you really want to protect users from the behavior of pages, you'd
really need to make creating the context cheap.
This was exactly my reaction as
On Sep 10, 2012, at 8:14 PM, Dean Jackson d...@apple.com wrote:
I propose adding a new method to HTMLCanvasElement:
interface HTMLCanvasElement : HTMLElement {
boolean supportsContext(DOMString contextId, any... arguments);
};
supportsContext takes the same parameters as getContext, and
On Sep 10, 2012, at 9:32 PM, Dean Jackson d...@apple.com wrote:
On Sep 10, 2012, at 12:28 PM, Tobie Langel tobie.lan...@gmail.com wrote:
On Sep 10, 2012, at 8:14 PM, Dean Jackson d...@apple.com wrote:
I propose adding a new method to HTMLCanvasElement:
interface HTMLCanvasElement
This is actually what we could do now. We could hide
window.WebGLRenderingContext
when we can't create one. But then we'd have to hide all these too:
attribute [Conditional=WEBGL] WebGLActiveInfoConstructor
WebGLActiveInfo;
attribute [Conditional=WEBGL]
On Tue, Sep 11, 2012 at 12:52 AM, Glenn Maynard gl...@zewt.org wrote:
On Mon, Sep 10, 2012 at 5:39 PM, Tobie Langel tobie.lan...@gmail.com
wrote:
It's too late; WebGL is a shipping, widely-used API. (This isn't a
WebGL
problem, either; it's just doing what every other API on the platform
On Fri, Sep 7, 2012 at 6:35 AM, Ian Hickson i...@hixie.ch wrote:
On Thu, 30 Aug 2012, Jonas Sicking wrote:
I think while in theory we could rely on UAs to enable barcode entry
anywhere, which definitely would provide the maximum capabilities for
the user. In practice it seems hard to create
I apologize in advance, as this is slightly off-topic. I've been
unsuccessfully looking for info on how Canvas hardware acceleration
actually works and haven't found much.
Would anyone have pointers?
Thanks.
--tobie
On Aug 14, 2012, at 21:21, Glenn Maynard gl...@zewt.org wrote:
(I've reordered my responses to give a more logical progression.)
On Tue, Jul 17, 2012 at 9:23 PM, Andrea Marchesini b...@mozilla.com wrote:
// The getFilenames handler receives a list of DOMString:
var handle =
On Mon, Aug 13, 2012 at 6:39 PM, Henri Sivonen hsivo...@iki.fi wrote:
If it indeed is the case that there are really only two realistic
bitmaps samplings for catering to differences in weeding device pixel
density (ignoring art direction), it would make sense to have simply
img
38 matches
Mail list logo
