Re: [whatwg] Challenging canvas.supportsContext

On Wed, Jun 19, 2013 at 11:29 AM, Boris Zbarsky wrote: > On 6/19/13 2:17 PM, Benoit Jacob wrote: >> The closest thing that I could find being discussed, was use cases by JS >> frameworks or libraries that already expose similar feature-detection >> APIs. >> However, that only shifts the question t

Re: [whatwg] Challenging canvas.supportsContext

On Wed, Jun 19, 2013 at 11:17 AM, Benoit Jacob wrote: > So let's look at the naive application usage pattern for supportsContext: > > if (canvas.supportsContext("webgl")) { > context = canvas.getContext("webgl"); > } > > The problem is that the same can be achieved with just the getContext

Re: [whatwg] How works Promise.any() if it was called with resolved promises?

On Fri, Jun 14, 2013 at 5:36 PM, Tetsuharu OHZEKI wrote: > 2013/6/15 Tab Atkins Jr. : >> On Fri, Jun 14, 2013 at 5:00 PM, Tetsuharu OHZEKI >> wrote: >> If you check out the spec, Promise.any() runs down its list of >> arguments in order, giving them the ability to reso

Re: [whatwg] How works Promise.any() if it was called with resolved promises?

On Fri, Jun 14, 2013 at 5:00 PM, Tetsuharu OHZEKI wrote: > Thank you. > > By the way, if we call `Promise.any()` with some resolved and rejected > promises and add new fulfillCallback to it, will the fulfillCallback > be invoked once with parameters which are values of all promises > passed to `P

Re: [whatwg] How works Promise.any() if it was called with resolved promises?

On Fri, Jun 14, 2013 at 2:25 PM, Tetsuharu OHZEKI wrote: > I have questions about DOM Promise. > > If we call `Promises.any()` with resolved promises, how does it > execute its fulfillCallback? The returned promise is immediately fulfilled, so the callback will be called in the next tick. Rememb

Re: [whatwg] Fetch: please review! (Anne van Kesteren)

On Fri, May 24, 2013 at 7:46 AM, alonisser wrote: > some input (I know, I'm a newbie in this mailing list so maybe i'm stating > or asking the obvious, atleast for everyone else): > >1. for clarity: The legacy chapter should be near the end and not the >first chapter, I couldn't understand

Re: [whatwg] Proposing: "autoscroll" event

On Tue, May 14, 2013 at 2:31 PM, Nils Dagsson Moskopp wrote: > Kyle Simpson schrieb am Tue, 14 May 2013 16:08:17 > -0500: >> There have been times this automatic behavior has been quite annoying >> because of accidential ID/hash overlap. > > Please explain how a document subresource can be “accid

Re: [whatwg] API to delay the document load event

On Thu, Apr 25, 2013 at 5:15 PM, Bjoern Hoehrmann wrote: > * Glenn Maynard wrote: >>This seems a bit heavy-handed. For these use cases, it doesn't seem like >>you need to delay the whole onload event, which would have tons of >>side-effects on the page. You could just tell the browser that you'r

Re: [whatwg] Comments on

On Mon, Apr 22, 2013 at 12:38 PM, Ian Hickson wrote: > On Mon, 22 Apr 2013, Matt Falkenhagen wrote: >> 3. For centering in the viewport, the spec mandates that the used value >> of 'top' be specially calculated. I found it more convenient to >> implement by mutating the computed value rather than

Re: [whatwg] 2D canvas feature proposal: text decoration

On Thu, Apr 18, 2013 at 4:42 PM, Rik Cabanier wrote: > On Thu, Apr 18, 2013 at 4:18 PM, Tab Atkins Jr. > wrote: >> On Thu, Apr 18, 2013 at 3:40 PM, Rik Cabanier wrote: >> > I think that all enumerated DOMStrings in CanvasDrawingStyles should >> > move >> >

Re: [whatwg] 2D canvas feature proposal: text decoration

On Thu, Apr 18, 2013 at 3:40 PM, Rik Cabanier wrote: > I think that all enumerated DOMStrings in CanvasDrawingStyles should move > to enums. This seems cleaner and have no compatibility issues. > However, if we keep them as DOMStrings, I agree that textDecoration should > be one too. If they're t

Re: [whatwg] 2D canvas feature proposal: text decoration

On Thu, Apr 18, 2013 at 1:37 PM, David Dailey wrote: > You know, I'm not quite sure why we have text in canvas at all. It's not > really text you know -- it's just a bunch of pixels. You can't select it, > you can't copy it to the clipboard, it's not accessible without a bunch of > effort that aut

Re: [whatwg] Add an attribute for opting out of synchronous CSSOM access

On Wed, Apr 17, 2013 at 2:51 PM, David Bruant wrote: > Le 05/04/2013 15:07, Henri Sivonen a écrit : >> Please add an attribute to that: >> * opts an external style sheet out of synchronous CSSOM access > > Sorry if my suggestion is naive, but why about an attribute to opt out of > CSSOM entirel

Re: [whatwg] definition not compatible with existing user-agent user interfaces

On Thu, Apr 4, 2013 at 2:12 PM, Boris Zbarsky wrote: > The way is defined, the document URI does not in any way > encode the document contents. > > Unfortunately, that breaks user-agent and extension features like "open > frame in new window", "show only this frame", "open frame in new tab", etc.

Re: [whatwg] Allowing authors to obtain a vertical

On Fri, Mar 29, 2013 at 10:27 AM, Ian Hickson wrote: > Why wouldn't this be a CSS issue? That's the layer of the Web platform > where we put presentationa-specific things. You can't detect the size of something from within CSS, because then you can change the size. > But in this particular case,

Re: [whatwg] Why are we merging Document and HTMLDocument again?

On Tue, Mar 5, 2013 at 12:42 PM, Boris Zbarsky wrote: > On 3/5/13 3:30 PM, Ian Hickson wrote: >> I'd be fine with having a Document descendant that is used for Documents >> that have global scopes / browsing contexts / the works, and one that is >> used for Documents that don't (e.g. createDocumen

Re: [whatwg] Why do we have and ?

On Tue, Feb 12, 2013 at 9:39 AM, Jukka K. Korpela wrote: > 2013-02-12 19:26, Tab Atkins Jr. wrote: >> The fact that authors today have a random assortment of displays for >> the exact same feature (credit card expirys) is something that would >> be great to fix, not bemoan a

Re: [whatwg] Why do we have and ?

On Tue, Feb 12, 2013 at 9:20 AM, Mounir Lamouri wrote: > On 01/02/13 15:39, Glenn Maynard wrote: >> FYI, I would find this annoying. CC expiry entry forms are typically >> select boxes containing 01-12. The text lines up with what's on my credit >> card, so I don't have to translate "07" to "Jul

Re: [whatwg] Canonical Image and Color

On Mon, Feb 11, 2013 at 4:17 PM, Brian Blakely wrote: > Sure thing. Let me go through the use cases that I see as applicable today, > derived from instances where an existing vendor or service currently > utilizes a non-standard implementation. > > * Social network sharing > > Facebook currently

Re: [whatwg] Canonical Image and Color

On Mon, Feb 11, 2013 at 2:33 PM, Brian Blakely wrote: > * Proposal > > Meta elements for defining a canonical image and color to be associated > with the page(s) in which they are included. This is intended for use by > user agents and third-party applications (such as social networks), > referre

Re: [whatwg] Polling APIs in JavaScript vs Callbacks

On Thu, Feb 7, 2013 at 6:32 PM, Glenn Maynard wrote: > This is just to say: callbacks are the pattern on on the platform, not > polling, and WebGL should follow that pattern, not go its own way and make > up its own conventions. If people don't understand why the platform's > conventions are what

Re: [whatwg] proposal: Add support for masking to canvas

On Tue, Jan 29, 2013 at 9:04 PM, Boris Zbarsky wrote: > On 1/29/13 11:37 PM, Rik Cabanier wrote: >> >> So the API could be as follows: > > ... > >> unrestricted double? sx; >> unrestricted double? sy; > > > Do these actually need to be nullable? What's the use case for setting them > to null? > >

Re: [whatwg] proposal: Add support for masking to canvas

On Tue, Jan 29, 2013 at 8:37 PM, Rik Cabanier wrote: > So the API could be as follows: > > enum CanvasMaskType { luminosity, alpha}; > dictionary maskOptions { > > CanvasImageSource image; > unrestricted double? sx; > unrestricted double? sy; > unrestricted double? sw; > unrestricted double? sh; >

Re: [whatwg] remove resetClip from the Canvas 2D spec

On Tue, Jan 29, 2013 at 6:10 PM, Rik Cabanier wrote: > It restores the graphics state back to the state at 'save' time and this > includes the clip area. > 'Clip' is a nested operation so every clip will be the intersection of the > existing clip area and the new one. > > PDF also has no initclip/

Re: [whatwg] proposal: Add support for masking to canvas

On Tue, Jan 29, 2013 at 7:30 PM, Rik Cabanier wrote: > Do you believe it's OK to have 12 arguments or would a dictionary be better? No, it's not okay. ^_^ Particularly when some of the parameters are boolean - boolean positional arguments are the devil. Go with a dict. ~TJ

Re: [whatwg] remove resetClip from the Canvas 2D spec

On Tue, Jan 29, 2013 at 5:00 PM, Rik Cabanier wrote: > All, > > we were looking at how resetClip [1] could be implemented in WebKit. > Looking over the Core Graphics implementation, this feature can't be > implemented without significant overhead. I also found an email from 2007 > where Maciej sta

Re: [whatwg] scoped style sheets and @-rules

On Mon, Jan 21, 2013 at 6:39 AM, L. David Baron wrote: > I thought I'd brought this issue up before, but I can't seem to find > a record of it. > > http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped > currently says that, inside scoped style sheets, @page

Re: [whatwg] Forms-related feedback

On Wed, Jan 16, 2013 at 1:03 AM, Bronislav Klučka wrote: > On 16.1.2013 8:23, Jukka K. Korpela wrote: >> Since the use cases are rare, is it better to force browser vendors to >> develop code to implement it, in their own ways, than to let various >> software developers set up libraries for it? Si

Re: [whatwg] Proposal: Add CanvasRenderingContext2D.fillRule with "nonzero" (default) and "evenodd" options

On Wed, Jan 9, 2013 at 11:42 AM, Rik Cabanier wrote: > Do people have an opinion on a boolean value vs an enum? > A boolean value is slightly faster to execute and type while an enum is > more descriptive. > > So far, canvas has not used enum values before. I strongly prefer enums for cases where

Re: [whatwg] and friends

On Sat, Dec 29, 2012 at 10:17 AM, David Young wrote: > On Sat, Dec 29, 2012 at 01:23:20AM +, Ian Hickson wrote: >> On Sun, 23 Oct 2011, Eric Sh. wrote: >> > >> > I was trying out the HTML5 context menu in firefox and I saw that there >> > is no way(in the specs) to create an empty menu with on

Re: [whatwg] Styling

On Jan 2, 2013 8:25 AM, "fantasai" wrote: > > On 04/08/2011 05:05 AM, Lachlan Hunt wrote: >> >> >> One option is to define that the list-style-type 'disclosure-*' as magic values that mean to render a UA specific/platform >> dependent widget. But that differs from all other list-style-type values

Re: [whatwg] Sortable Tables

On Dec 27, 2012 6:04 PM, "Ian Hickson" wrote: > > 2. What values should the sort property allow. One idea is that it takes > > a JS function similar to what JavaScript's sort function takes. If you > > leave it out then it just does alphanumeric sort. > > I was going to have a comparator function,

Re: [whatwg] Feature Request: Media Elements as Targets for Links

On Mon, Dec 17, 2012 at 4:37 PM, Ian Hickson wrote: > On Sat, 24 Nov 2012, Nils Dagsson Moskopp wrote: >> Use Case Description: >> >> Linking to specific fragments of media is possible via media fragment >> URIs [1]. However, it is not possible to apply a link to embedded >> media declarativ

Re: [whatwg] Magical alignment and moving anchor targets

On Tue, Dec 11, 2012 at 10:45 AM, Matt Falkenhagen wrote: > The spec seems unclear on whether a magically aligned element[1] should > follow its anchor when its anchor moves, e.g., by dynamic style changes or > something like CSS animations. > > I think we want the element to follow the anchor. If

Re: [whatwg] Cycles in anchored positioning

On Fri, Dec 7, 2012 at 3:58 PM, Matt Falkenhagen wrote: > How are cycles with magically aligned[1] elements resolved? > > For example, if a and b are dialogs and you do: > > a.show(b); > b.show(a); > > I think an anchoring cycle can also occur if an element |a| is anchored to > a descendent of an

Re: [whatwg] Make DOMStringMap constructable, and el.dataset writeable?

On Fri, Nov 30, 2012 at 1:31 PM, Boris Zbarsky wrote: > On 11/30/12 2:23 PM, Tab Atkins Jr. wrote: >> It would be somewhat cleaner if she could simply construct a >> DOMStringMap and assign it, like so: >> >> for(var i = 0; i < cards.length; i++) { >>

Re: [whatwg] Make DOMStringMap constructable, and el.dataset writeable?

On Fri, Nov 30, 2012 at 4:01 PM, Ian Hickson wrote: > On Fri, 30 Nov 2012, Tab Atkins Jr. wrote: >> She's making a game, where the game initialization script expects >> certain types of elements, and for the initial state data of the >> elements to be present in data

Re: [whatwg] URL: URLQuery

On Fri, Nov 30, 2012 at 10:02 AM, Alexandre Morgaut wrote: >> Only feedback left is the return types of set(), append(), and delete(). > > Maybe remove() would be better than delete() as delete is a reserved JS > keyword ;-) Nope, it's contextually reserved. You can use in places like a method

Re: [whatwg] URL: URLQuery

On Fri, Nov 30, 2012 at 9:47 AM, Anne van Kesteren wrote: > On Fri, Nov 30, 2012 at 6:42 PM, Tab Atkins Jr. wrote: >> Only feedback left is the return types of set(), append(), and delete(). >> >> In Maps, set() returns the map, so you can chain more easily. TC39 >

[whatwg] Make DOMStringMap constructable, and el.dataset writeable?

Currently, el.dataset is readonly. A friend of mine passed along a use-case for making it writeable. She's making a game, where the game initialization script expects certain types of elements, and for the initial state data of the elements to be present in data attributes on them. She'd like to

Re: [whatwg] URL: URLQuery

On Fri, Nov 30, 2012 at 9:17 AM, Anne van Kesteren wrote: > On Sat, Oct 13, 2012 at 12:24 AM, Tab Atkins Jr. wrote: >> If we do stick with the method-based map, I strongly feel we should >> match the JS Map API, and have a has() method as well. *Ideally*, >> this would

Re: [whatwg] Menus and Toolbars

On Tue, Nov 27, 2012 at 4:12 PM, Ian Hickson wrote: > To move forward on this, here are some proposals: > > #1: Drop and all related features. I don't think we should do this, > but if we can't get agreement on what to implement, this is the only > option left, so it's on the table. I'm gonna th

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

On Sat, Nov 24, 2012 at 7:10 PM, Adam Barth wrote: > 2) Remarkably, the current best candidate is a rendering pipeline that > attempts to use the DOM in immediate mode. The application performs > some application-specific processing to determine which portions of > the model can actually affect w

Re: [whatwg] [URL] DOM API Feedback

On Mon, Nov 19, 2012 at 5:38 AM, Boris Zbarsky wrote: > On 11/19/12 2:36 AM, David Bruant wrote: >>> I suppose the same goes for ES6 Map. >> >> As Tab suggested, a Map subclass could certainly work > > How close are "subclasses" to not being vaporware (both in spec and > implementation terms)? Sp

Re: [whatwg] [URL] DOM API Feedback

On Mon, Nov 19, 2012 at 8:22 AM, Boris Zbarsky wrote: > On 11/19/12 11:20 AM, Tab Atkins Jr. wrote: >> To a first approximation, they shouldn't be. ES6 classes desugar into >> functions and prototypes. > > Hmm. They didn't completely at some point, but maybe somet

Re: [whatwg] [URL] DOM API Feedback

On Mon, Nov 19, 2012 at 8:19 AM, Boris Zbarsky wrote: > On 11/19/12 11:16 AM, Tab Atkins Jr. wrote: >> Subclasses aren't anything new - we're just referring to the standard >> prototype-based subclassing. > > OK. That's different from ES6 classes/subc

Re: [whatwg] [URL] DOM API Feedback

On Sun, Nov 18, 2012 at 3:17 PM, Anne van Kesteren wrote: > On Sun, Nov 18, 2012 at 11:34 PM, David Bruant wrote: >> I feel the URLQuery object could be a regular object. Or maybe an ES6 Map. >> If not an ES6 Map, maybe its API could be mapped exactly to ES6 Map. It >> would increase interoperabi

Re: [whatwg] Canvas in Workers

On Fri, Nov 16, 2012 at 1:03 PM, Oliver Hunt wrote: > postMessage already has an ownership transfer list, we could always extend > the set of transferable types to include a canvas like thing (the context or > some such). Transferring contexts is tolerable for 2d, but a non-starter for webgl -

Re: [whatwg] hidden="" should be "display:none !important" in the UA stylesheet

On Tue, Nov 13, 2012 at 1:49 PM, Edward O'Connor wrote: > Hi, > > I don't recall if this was in person or in email, but I think Tab made a > compelling argument in favor of changing the implementation of hidden="" > to be > > [hidden] { > display: none !important; > } > > in the UA stylesh

Re: [whatwg] Including

On Mon, Nov 12, 2012 at 10:41 PM, Mark Nottingham wrote: > I've maintained a little library for a while that does inclusion: > https://github.com/mnot/hinclude > http://mnot.github.com/hinclude/ > > It's used in a few different places, and is now part of Symfony > , appare

Re: [whatwg] Sortable Tables

On Thu, Nov 8, 2012 at 8:59 AM, Ojan Vafai wrote: > On Thu, Nov 8, 2012 at 4:17 AM, Alex Russell wrote: >> I'm much more inclined to solve this from the data axis. Asking the table >> itself to do the sorting is weird. Instead, you most often want to have >> some data source return you rows in so

Re: [whatwg] Should scrollbars move focus?

On Fri, Oct 19, 2012 at 3:34 PM, Elliott Sprehn wrote: > I was working on a bug [1][2] recently where authors had complained > about WebKit's behavior where clicking a scrollbar unfocuses the > activeElement. What's particularly quirky is that the window scrollbar > never moves focus in any browse

Re: [whatwg] checksum attribute in a href tag

On Fri, Oct 19, 2012 at 11:46 AM, A. Rauschenbach wrote: > Am 2012-10-19 18:49, schrieb Ian Hickson: >> What is the attack scenario you are trying to avoid? >> >> Without a discussion of what problem you're trying to solve, it's unclear >> how to evaluate the proposal. >> >> The idea of a hash=""

Re: [whatwg] Separating intrinsic sizing out from the iframe seamless attribute

On Thu, Oct 18, 2012 at 4:14 PM, Ian Hickson wrote: > On Wed, 18 Jul 2012, Jonathan Watt wrote: >> The use cases are simple. I want to be able to embed SVG as-a-document >> (not as-an-image) and have it size to its intrinsic size, without >> messing up the style of the SVG. > > That's not a use ca

Re: [whatwg] HTML 5 should include a way to create custom page header & footer for printing.

On Sun, Oct 14, 2012 at 12:10 AM, Mircea LUTIC wrote: > HTML 5 should include a way to create custom page header & footer for > printing. > These should allow to include images > > I think it should be something like > > > My company softwareThe best software on > the planet > > > ... This

Re: [whatwg] URL: URLQuery

On Sat, Oct 13, 2012 at 1:39 PM, Mike Dierken wrote: > Since a URL query string is not a strict map with only one value for a > key, would the get/set operations allow for an array as well as an > atomic value? Yes. Regardless of the getters vs get() discussion, I think there was consensus on th

Re: [whatwg] URL: URLQuery

On Fri, Oct 12, 2012 at 9:10 AM, Anne van Kesteren wrote: > I didn't really get around to working on URLs this week like I > planned, but I managed to draft the query API that was discussed in > the last thread: > > http://url.spec.whatwg.org/#urlutils > > get() returns the first value. getAll() r

Re: [whatwg] Issues with microdata and proposals for improvements

On Fri, Oct 12, 2012 at 7:28 AM, pghj wrote: > == Incompatible property names when using itemrefs == > > Consider the following piece of HTML: > > http://schema.org/Book"; itemref="a"> ... > http://schema.org/LiteraryEvent"; itemref="b"> > ... > itemtype="http://schema.org/Person"; itemref="c">

Re: [whatwg] Features for responsive Web design

On Tue, Oct 9, 2012 at 11:48 AM, Ian Hickson wrote: > On Tue, 9 Oct 2012, Mark Callow wrote: >> On 2012/10/06 7:09, Ian Hickson wrote: >> > I agree, when there's 3x displays, this could get to the point where we >> > need to solve it. :-) >> >> With the current displays, it's just not that big a d

Re: [whatwg] [canvas] Path object

On Tue, Oct 2, 2012 at 6:34 PM, Charles Pritchard wrote: > On Oct 2, 2012, at 6:25 PM, "Tab Atkins Jr." wrote: >> On Tue, Oct 2, 2012 at 6:22 PM, Charles Pritchard wrote: >>> I wanted vendors to solidify consensus on a version close to what currently >&g

Re: [whatwg] [canvas] Path object

On Tue, Oct 2, 2012 at 6:22 PM, Charles Pritchard wrote: > I wanted vendors to solidify consensus on a version close to what currently > exists, with minor changes for accessibility. The WHATWG and W3C have chosen > instead to make broad changes, as proposed in version 5/the Hixie-Atkins > draf

Re: [whatwg] [canvas] Path object

On Tue, Oct 2, 2012 at 4:58 PM, Elliott Sprehn wrote: > What of the fact that this breaks existing pages with id="Path"> that access it as just Path? Historically this has been a > non-starter for new APIs. It would have been useful to bring this up as a problem in your original email. ^_^ I h

Re: [whatwg] [canvas] Path object

On Sat, Sep 22, 2012 at 9:17 PM, Elliott Sprehn wrote: > I was looking at the canvas Path API and had some concerns. In > particular it's inconsistent with the rest of canvas: > > We already have CanvasGradient and CanvasPattern in the global > namespace, so this should probably be called CanvasPa

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Mon, Sep 24, 2012 at 4:32 PM, Ian Hickson wrote: > On Mon, 24 Sep 2012, Tab Atkins Jr. wrote: >> Returning to the original subject, we don't *want* optional arguments >> here. > > Well, the canvas API has optional arguments, so there's no way to be > consisten

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Mon, Sep 24, 2012 at 3:50 PM, Ian Hickson wrote: > On Mon, 24 Sep 2012, Tab Atkins Jr. wrote: >> You are looking at the simplest possible use-case for A/a, nearly the >> only case that can be done without trig, where you're starting and >> stopping the arc at a qu

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Mon, Sep 24, 2012 at 1:14 PM, Ian Hickson wrote: > On Mon, 24 Sep 2012, Tab Atkins Jr. wrote: >> > >> > Omitting two numbers, one of which is zero, is easily no more a win >> > than the cost of having two different nearly-identical commands. Just >> > c

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Mon, Sep 24, 2012 at 11:51 AM, Ian Hickson wrote: > On Sun, 23 Sep 2012, Tab Atkins Jr. wrote: >> On Sun, Sep 23, 2012 at 3:57 PM, Ian Hickson wrote: >> > On Fri, 21 Sep 2012, Tab Atkins Jr. wrote: >> >> So, can we rename the 7-arg arcTo to ellipseTo? That seems

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Mon, Sep 24, 2012 at 6:59 AM, Rick Waldron wrote: > Has there been any discussion about moving newly emerging APIs to a single > "options object" formal parameter? This discussion is in the context of the SVG API, which is an attribute microsyntax. So, that's not possible for this. ^_^ How

Re: [whatwg] New URL Standard

On Mon, Sep 24, 2012 at 2:34 AM, Anne van Kesteren wrote: > I have been thinking about introducing a .query attribute that would > return a special interface for this purpose, but what the right API > should be seems somewhat tricky. Adam and Erik came up with a solution > that introduces eight ne

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Sun, Sep 23, 2012 at 3:57 PM, Ian Hickson wrote: > On Fri, 21 Sep 2012, Tab Atkins Jr. wrote: >> So, can we rename the 7-arg arcTo to ellipseTo? That seems to support >> your "always [require] all the arguments" recommendation. ^_^ > > Just have one arcTo comman

Re: [whatwg] Rename the 7-arg arcTo() to ellipseTo()?

On Thu, Sep 20, 2012 at 4:58 PM, Ian Hickson wrote: > On Mon, 17 Sep 2012, Tab Atkins Jr. wrote: >> Heya, we at the SVGWG just resolved today to add equivalents for the >> CanvasPathMethods interface arc/ellipse/arcTo commands to the >> element's syntax. >> >

Re: [whatwg] [canvas] matrix based changes on bitmaps

On Fri, Sep 21, 2012 at 8:34 AM, Tyler Larson wrote: > On Sep 21, 2012, at 9:49 AM, Rik Cabanier wrote: >> Support CSS Filters will satisfy this use case. >> There are a number of built-in filters (such as sepia and constrast) and >> even support for vertex and fragment shaders. >> The current s

[whatwg] Rename the 7-arg arcTo() to ellipseTo()?

Heya, we at the SVGWG just resolved today to add equivalents for the CanvasPathMethods interface arc/ellipse/arcTo commands to the element's syntax. Ideally, we'd be able to use the same names as Path, for minimal confusion - "" producing a line from (0,0) to (40,30), then a quarter-arc to (30,40

Re: [whatwg] Including HTML more directly into SVG

On Tue, Sep 11, 2012 at 12:37 PM, Elliott Sprehn wrote: > On Sep 11, 2012 11:35 AM, "Tab Atkins Jr." wrote: >> On Tue, Sep 11, 2012 at 11:29 AM, Elliott Sprehn >> wrote: >> > On Tue, Sep 11, 2012 at 9:09 AM, Tab Atkins Jr. >> > wrote: >>

Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element

On Thu, Sep 13, 2012 at 11:09 AM, Jukka K. Korpela wrote: > And I suppose by weird formation you mean the example that starts with > > > >> >Graduation Ceremony Summer 2022> >> > >> can anybody tell me if this is known/on purpous > > > My guess is that it's an accidental resul

Re: [whatwg] Including HTML more directly into SVG

On Tue, Sep 11, 2012 at 11:29 AM, Elliott Sprehn wrote: > On Tue, Sep 11, 2012 at 9:09 AM, Tab Atkins Jr. wrote: >> ... >> >>> The paragraph and span concept in SVG >>> wouldn't be the same thing so it's not an antipattern. You would have >>>

Re: [whatwg] Including HTML more directly into SVG

On Tue, Sep 11, 2012 at 1:23 AM, Elliott Sprehn wrote: > On Tue, Sep 11, 2012 at 1:15 AM, Elliott Sprehn wrote: >> On Mon, Sep 10, 2012 at 4:59 PM, Tab Atkins Jr. wrote: >> >>... >>> >>> Another solution could be SVG inventing their own elements for thes

Re: [whatwg] Including HTML more directly into SVG

n Tue, Sep 11, 2012 at 1:15 AM, Elliott Sprehn wrote: > On Mon, Sep 10, 2012 at 4:59 PM, Tab Atkins Jr. wrote: >> ... >> >> This would be a lot easier if I could somehow invoke the CSS box model >> inside of SVG, ... > > This tightly binds the list of eleme

[whatwg] Including HTML more directly into SVG

This is a continuation of a discussion started in the #whatwg IRC room, so I'll start somewhat abruptly. 1. Check out . See all those boxes full of text in the diagrams? Looks simple, right? Just a box filled with text, with a border an

Re: [whatwg] srcset isn't future-friendly to screen size differences

On Fri, Sep 7, 2012 at 9:21 AM, Hans Muller wrote: > On 9/6/12 6:36 PM, "Tab Atkins Jr." wrote: >>Consider the following example: >> >> >> >>For a screen that's somewhere near 800px wide, this works just fine. >>However, a 1x screen 1600

[whatwg] srcset isn't future-friendly to screen size differences

This email is an extension of the thread started at by John Mellor, distilling the core problem he has into a more easily-understood and digested form. The srcset attribute, as currently written, is not friendly to large

Re: [whatwg] Should editable elements have placeholder attribute?

On Thu, Sep 6, 2012 at 3:56 AM, Aryeh Gregor wrote: > It should never be possible to make a contenteditable element contain > nothing, once it has something in it, because then it would collapse > to zero height and you wouldn't be able to click on it. (IIRC, some > browsers have non-standard spe

Re: [whatwg] Hardware accelerated canvas

On Tue, Sep 4, 2012 at 10:07 AM, David Geary wrote: > On Tue, Sep 4, 2012 at 10:53 AM, Boris Zbarsky wrote: >> Ms2ger points out (without endorsing) that there's an: >> >> 8) Have every author who wants their canvas to stick around call >> toDataURL() and stick the result in an . > > And then th

Re: [whatwg] input type=barcode?

On Thu, Aug 30, 2012 at 11:59 AM, Mounir Lamouri wrote: > On 08/30/2012 12:12 PM, Tab Atkins Jr. wrote: >> It shouldn't be a new input type, because it's not a *type* of value. >> Barcodes are simple a wrapper for a value, to make it more easily >> machine-read

Re: [whatwg] input type=barcode?

On Thu, Aug 30, 2012 at 8:07 AM, Mounir Lamouri wrote: > On 08/27/2012 07:01 PM, Andy Davies wrote: >> On 27 August 2012 20:25, Tab Atkins Jr. wrote: >>> On Mon, Aug 27, 2012 at 10:56 AM, Ian Hickson wrote: >>>>> >>>>> True, so this is perh

Re: [whatwg] Support for

On Tue, Aug 28, 2012 at 11:04 AM, Boris Zbarsky wrote: > I just added support for in Gecko.[1] > Such links are subject to CORS checks if the load is cross-site, and the > sheet load will fail if the CORS check fails. If the CORS check succeeds, > script in the page will be able to script the cr

Re: [whatwg] input type=barcode?

On Mon, Aug 27, 2012 at 10:56 AM, Ian Hickson wrote: > On Wed, 3 Aug 2011, Tab Atkins Jr. wrote: >> On Wed, Aug 3, 2011 at 8:50 AM, Randy wrote: >> > On top of that, the vast majority of these readers just translate it >> > back to text. It's just another input

Re: [whatwg] Serialization of expandos on String / Boolean / Number objects

On Thu, Aug 23, 2012 at 12:13 PM, Dumez, Christophe wrote: > Hi, > > The latest specification of the structured clone algorithm [1] does > not indicate that we are supposed to serialize expandos on objects > such as String, Boolean or Number. > > For example: > var str = new String("test"); > str.

Re: [whatwg] Sychronous operations in onclose handlers

On Wed, Aug 22, 2012 at 8:50 AM, Mark Watson wrote: > Hi everyone, > > I heard that there was some discussion of banning the use of synchronous > operations within document onclose handlers. > > Whilst it is obviously bad to hold up the closing of a document - especially > indefinitely - I wonde

Re: [whatwg] img srcset / css image-set issues

On Wed, Aug 22, 2012 at 4:22 AM, John Mellor wrote: > On Wednesday, August 22, 2012, Tab Atkins Jr. wrote: >> I doubt this is actually what you want, though - you're probably not >> actually trying to cater to devices with an 8:1 pixel ratio! (Those >> may not ever exis

Re: [whatwg] img srcset / css image-set issues

On Tue, Aug 21, 2012 at 4:28 PM, John Mellor wrote: > On Tue, Aug 21, 2012 at 8:31 PM, Tab Atkins Jr. > wrote: >> >> On Tue, Aug 21, 2012 at 12:20 PM, John Mellor wrote: >> > 1. Neither is of any use for flexibly-sized images. >> >> This is what Media Que

[whatwg] Consider making @srcset do fallback?

Currently, the CSS image-set() function (sister spec to ) is specified to do fallback to the less-desirable options if the first choice doesn't load or can't be decoded. I specified it this way because it seemed reasonable, and it's how the similar image() function works (which is specifically des

Re: [whatwg] img srcset / css image-set issues

On Tue, Aug 21, 2012 at 12:31 PM, Tab Atkins Jr. wrote: > On Tue, Aug 21, 2012 at 12:20 PM, John Mellor wrote: >> CSS image-set and HTML img srcset are getting their first implementations >> but both APIs have serious shortcomings. We should fix them before it's too >>

Re: [whatwg] img srcset / css image-set issues

On Tue, Aug 21, 2012 at 12:20 PM, John Mellor wrote: > CSS image-set and HTML img srcset are getting their first implementations > but both APIs have serious shortcomings. We should fix them before it's too > late: > > 1. Neither is of any use for flexibly-sized images. > 2. srcset isn't as smart/

Re: [whatwg] [selectors4] drag-and-drop pseudo-classes

On Wed, Aug 15, 2012 at 9:12 AM, Henri Sivonen wrote: > On Aug 14, 2012 10:54 PM, "Tab Atkins Jr." wrote: >> On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa wrote: >>> Yeah, and that's not compatible with how drag and drop are implemented >>> on >&g

Re: [whatwg] [selectors4] drag-and-drop pseudo-classes

On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa wrote: > I'm asking how we're supposed to implement this pseudo-classes given that > the only way to know whether an element can receive the item is by firing > dragenter and/or dragover events. e.g. No, we can know it declaratively via the dropzone

Re: [whatwg] [selectors4] drag-and-drop pseudo-classes

On Tue, Aug 14, 2012 at 3:03 AM, Sebastian Zartner wrote: >> * One for all elements representing possible drop targets >> that could receive the item. >> * One for all elements representing drop targets that do >> not accept this type of item. > > This sounds like these two pseudo-clas

Re: [whatwg] [selectors4] drag-and-drop pseudo-classes

On Mon, Aug 13, 2012 at 11:55 PM, Ryosuke Niwa wrote: > On Mon, Aug 13, 2012 at 9:19 PM, fantasai > wrote: >> The CSSWG discussed drag-and-drop pseudo-classes today. The current >> proposal is to have three pseudo-classes: >> >> * One for the element representing the drop target that >> wou

Re: [whatwg] Wasn't there going to be a strict spec?

On Fri, Aug 10, 2012 at 5:02 PM, Erik Reppen wrote: > Browser vendor politics I can understand but if we're going to talk about > what "history shows" about people like myself suggesting features we can't > actually support I'd like to see some studies that contradict the > experiences I've had as

Re: [whatwg] Wasn't there going to be a strict spec?

On Fri, Aug 10, 2012 at 3:29 PM, Erik Reppen wrote: > This confuses me. Why does it matter that other documents wouldn't work if > you changed the parsing rules they were defined with to stricter versions? > As far as backwards compatibility, if a strict-defined set of HTML would > also work in a

<    1   2   3   4   5   6   7   8   9   10   >