[whatwg] Standards development happening on GitHub

I wanted to remind the mailing list that currently all WHATWG standards are being developed on GitHub. This enables everyone to directly change standards through pull requests and start topic-based discussion through issues. GitHub is especially useful now that the WHATWG covers many more topics

Re: [whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

That's right. From discussions with Mozilla I don't think that code path's enabled in their implementation yet, but it will be (as well as in Chrome's future implementation of the same spec). On Sat, Jan 23, 2016 at 12:40 PM, Gregg Tavares wrote: > Never mind me. For

Re: [whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

I presume you're supposed to just postMessage back to the main thread when you commit(). The spec should probably have a "commit" event though. On Jan 23, 2016 1:49 PM, "Gregg Tavares" wrote: > I just noticed Firefox shipped an OffscreenCanvas implementation. Looking > at the

[whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

I just noticed Firefox shipped an OffscreenCanvas implementation. Looking at the spec it seems there is no way to synchronize updates from a worker with dom/css manipulations. Was this already discussed? There are web apps that synchronize HTML dom elements with canvas updates. I'm sure they'd

Re: [whatwg] OffscreenCanvas from a worker and synchronization with DOM/CSS

Never mind me. For whatever reason my mind blanked out. You can transfer to the main thread and then apply to a canvas.

Re: [whatwg] Using time-origin-relative times for the .timeStamp property of animation events is not web-compatible

rg/show_bug.cgi?id=1231619#c3 for details. Added a note to the corresponding issue: https://github.com/whatwg/dom/issues/23#issuecomment-163740275 -- https://annevankesteren.nl/

Re: [whatwg] Signature Link Relation for Cryptographic Resource Verification

On Wed, Dec 9, 2015 at 10:05 AM, Sean B. Palmer wrote: > I expect that I will be continuing this discussion largely with the > WebAppSpec team, as their work is so obviously related to the contents > of the Internet-Draft. Thank you, that does indeed seem like the right

[whatwg] Using time-origin-relative times for the .timeStamp property of animation events is not web-compatible

It looks like at least the angular-animate assumes that the .timeStamp property of animation events produces values that can be compared to Date.now() return values. See https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c3 for details. -Boris

Re: [whatwg] Signature Link Relation for Cryptographic Resource Verification

Signature and hashes have different use cases. A signature guarantees that a person or organisation endorses a resource, as well as guaranteeing the integrity. A hash only guarantees the integrity. A signature should be given if a user is downloading software that must be proven to come from a

Re: [whatwg] Signature Link Relation for Cryptographic Resource Verification

here on GitHub where they have their issue tracker: https://github.com/w3c/webappsec/issues/449#issuecomment-163279813 I understand that the WHATWG list is more interested in listening to the problems before solutions are mooted, and as such my GitHub writeup goes into more background detai

Re: [whatwg] Signature Link Relation for Cryptographic Resource Verification

+1 --- Delfi Ramirez My digital signature [1] +34 633 589231 del...@segonquart.net [2] twitter: delfinramirez IRC: segonquart Skype: segonquart [3] http://segonquart.net http://delfiramirez.info [4] On 2015-12-08 16:44, Sean B. Palmer wrote: >

[whatwg] Signature Link Relation for Cryptographic Resource Verification

https://www.ietf.org/id/draft-palmer-signature-link-relation-00.txt -- Sean B. Palmer

Re: [whatwg] Signature Link Relation for Cryptographic Resource Verification

"Sean B. Palmer" , 2015-12-08 15:44 +: > > https://www.ietf.org/id/draft-palmer-signature-link-relation-00.txt Seems like the underlying use case is something Subresource Integrity is already intended to potentially be used to address.

[whatwg] ImageBitmap should have an origin-clean flag

Currently, createImageBitmap throws a security error when it encounters cross-origin content. This is unnecessarily restrictive IMHO. https://github.com/whatwg/html/pull/385

Re: [whatwg] Inclusion suggestion

Sent from Windows Mail From: 4723286...@gmail.com Sent: ‎Friday‎, ‎December‎ ‎04‎, ‎2015 ‎7‎:‎55‎ ‎PM To: wha...@whatwg.org If someone would implement the case of needing a place to put in markup in a location whereas other materials would move accordingly, in a dynamic way, that

Re: [whatwg] Splitting CanvasRenderingContext2D

Great, thanks all. I'll put together the start of a PR this week (just modifying the IDL) so that we can start discussing name / where everything goes. Thanks, Ian On Tue, Dec 1, 2015 at 12:11 PM, Justin Novosad wrote: > I think it may be possible to do this refactor without

Re: [whatwg] Splitting CanvasRenderingContext2D

On 12/1/15 11:40 AM, Domenic Denicola wrote: Since it has no web-visible impact That may or may not be true. For example, it's quite likely to change, in practice, the enumeration order for properties on the obect. Of course there is no spec defining that enumeration order right now... but

Re: [whatwg] Splitting CanvasRenderingContext2D

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Ian Kilpatrick > There are a couple of ways to split up the CanvasRenderingContext2D API, > namely adding inheritance + [NoInterfaceObject] to superclasses (as to not > change prototype chain, maybe not a large web compa

[whatwg] Splitting CanvasRenderingContext2D

Hi whatwg, (public-houd...@w3.org cc'd) For the CSS Paint API[1] work in Houdini we would like to split up the current CanvasRenderingContext2D to remove references to the DOM and pixel readback. Additionally OffscreenCanvas[2] needs a similar reduced subset of the CanvasRenderingContext2D api

[whatwg] Delivery reports about your e-mail

[whatwg] Interpretation of CanvasRenderingContext2D.closePath()

Hi All, The text in the spec: The closePath() method must do nothing if the object's path has no subpaths. Otherwise, it must mark the last subpath as closed, create a new subpath whose first point is the same as the previous subpath's first point, and finally add this new subpath to the path.

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 9:02 AM, Justin Novosad wrote: > Hi All, > > The text in the spec: > > > > The closePath() method must do nothing if the object's path has no > subpaths. Otherwise, it must mark the last subpath as closed, create a new > subpath whose first point is the

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

Also, the part about "repeating the last (possibly implied) moveTo() call" doesn't make much sense if we assume that closePath() applies to the new sub path that was started by the last moveTo() call. On Mon, Nov 16, 2015 at 12:38 PM, Justin Novosad wrote: > That makes sense,

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

That makes sense, but the text for closePath() talks about "the last subpath", which I guess is a bit unclear. On Mon, Nov 16, 2015 at 12:30 PM, Rik Cabanier wrote: > > > On Mon, Nov 16, 2015 at 9:02 AM, Justin Novosad wrote: > >> Hi All, >> >> The text in

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad wrote: > Also, the part about "repeating the last (possibly implied) moveTo() call" > doesn't make much sense if we assume that closePath() applies to the new > sub path that was started by the last moveTo() call. > It *is* super

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 1:40 PM, Rik Cabanier wrote: > > > On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad wrote: > >> Also, the part about "repeating the last (possibly implied) moveTo() >> call" doesn't make much sense if we assume that closePath()

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 10:54 AM, Justin Novosad wrote: > > > On Mon, Nov 16, 2015 at 1:40 PM, Rik Cabanier wrote: > >> >> >> On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad wrote: >> >>> Also, the part about "repeating the last (possibly

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 2:16 PM, Rik Cabanier wrote: > > > On Mon, Nov 16, 2015 at 10:54 AM, Justin Novosad wrote: > >> >> >> On Mon, Nov 16, 2015 at 1:40 PM, Rik Cabanier wrote: >> >>> >>> >>> On Mon, Nov 16, 2015 at 9:41 AM, Justin

Re: [whatwg] OffscreenCanvas

+Justin who gave a talk on this feature at BlinkOn. From: Anne van Kesteren Sent: Friday, November 13, 2015 09:54 To: WHATWG Subject: [whatwg] OffscreenCanvas Thanks to Olli I discovered https://wiki.whatwg.org/wiki/OffscreenCanvas is much further along than I thought. Is anyone planning

Re: [whatwg] OffscreenCanvas

Yes. I plan to transform that proposal into a PR soon-ish. But first I will submit a PR that removes proxy canvas and friends (which no one has implemented AFAIK).

[whatwg] OffscreenCanvas

Thanks to Olli I discovered https://wiki.whatwg.org/wiki/OffscreenCanvas is much further along than I thought. Is anyone planning on creating a PR against https://github.com/whatwg/html for the more formal specification of this feature? (And simultaneously ripping out the old worker canvas text

Re: [whatwg] Removing mediagroup/MediaController from HTML

On Tue, Nov 3, 2015 at 4:20 PM, David Singer <sin...@apple.com> wrote: > >> On Oct 3, 2015, at 13:39 , Silvia Pfeiffer <silviapfeiff...@gmail.com> wrote: >> >> On Fri, Oct 2, 2015 at 10:27 AM, Domenic Denicola <d...@domenic.me> wrote: >>> From

Re: [whatwg] VIDEO and pitchAdjustment

31, 2015 at 9:48 PM, Domenic Denicola <d...@domenic.me> wrote: >>>>>> From: Eric Carlson [mailto:eric.carl...@apple.com] >>>>>> >>> >>> [...] >>>> I've filed a spec issue to make it so: >>>> https://github.com/whatwg/html/issues/262 >>

Re: [whatwg] VIDEO and pitchAdjustment

gt;>> >>> From: Eric Carlson [mailto:eric.carl...@apple.com] >>> >>> >>> >>> [...] >>> > I've filed a spec issue to make it so: >>> > https://github.com/whatwg/html/issues/262 >>> > >>> > If there's any

Re: [whatwg] VIDEO and pitchAdjustment

m> wrote: >>> On Tue, Sep 1, 2015 at 11:21 AM, Philip Jägenstedt <phil...@opera.com> >>> wrote: >>>> On Mon, Aug 31, 2015 at 9:48 PM, Domenic Denicola <d...@domenic.me> wrote: >>>>> From: Eric Carlson [mailto:eric.carl...@apple.com] >

Re: [whatwg] VIDEO and pitchAdjustment

l...@apple.com] >>> [...] > I've filed a spec issue to make it so: > https://github.com/whatwg/html/issues/262 > > If there's any implementor interest in pitch control that goes beyond > (independently) or that, please file a separate issue. > They won't. You can hold th

Re: [whatwg] VIDEO and pitchAdjustment

at 9:48 PM, Domenic Denicola <d...@domenic.me> wrote: > >>> From: Eric Carlson [mailto:eric.carl...@apple.com] > >>> > > [...] > > I've filed a spec issue to make it so: > > https://github.com/whatwg/html/issues/262 > > > > If there's any i

Re: [whatwg] VIDEO and pitchAdjustment

lip Jägenstedt <phil...@opera.com> >> > wrote: >> >> On Mon, Aug 31, 2015 at 9:48 PM, Domenic Denicola <d...@domenic.me> >> >> wrote: >> >>> From: Eric Carlson [mailto:eric.carl...@apple.com] >> >>> >> >> [...] >

Re: [whatwg] Removing mediagroup/MediaController from HTML

> On Oct 3, 2015, at 13:39 , Silvia Pfeiffer <silviapfeiff...@gmail.com> wrote: > > On Fri, Oct 2, 2015 at 10:27 AM, Domenic Denicola <d...@domenic.me> wrote: >> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of >> >>> is removal really

Re: [whatwg] VIDEO and pitchAdjustment

use it didn't actually do anything in Chromium. > > In both Gecko and WebKit it defaults to true. Is there anything else > worth knowing before writing the spec for this? I've filed a spec issue to make it so: https://github.com/whatwg/html/issues/262 If there's any implementor interest in pitch control that goes beyond (independently) or that, please file a separate issue. Philip

[whatwg] F re

Sent from myMail for iOS

Re: [whatwg] VIDEO and pitchAdjustment

On 8/27/15, Robert O'Callahan wrote: > On Fri, Aug 28, 2015 at 6:02 AM, Garrett Smith > wrote: > [...] > But variable pitch control it would be useful for music adjustments >> like "over the mountain", "Black Star", "Take your Whiskey Home", all

Re: [whatwg] Proposal for showing thousand separator in form controls.

I'm afraid that we have never agreed until someone misused . Let's first decide what numbers is meant by number type. If our answer would be: https://en.wikipedia.org/wiki/Rational_number The years is the smallest part of all the numbers. Anyway always can use for them. Also a special case is

Re: [whatwg] Proposal for showing thousand separator in form controls.

On 10/15/15 9:58 AM, Михаил Гаврилов wrote: I understand an option to add an attribute to manually specify a delimiter is not considered here. I think this is the thing that has the best chance of success: having explicit opt-in to various different formatting behaviors based on knowledge of

Re: [whatwg] Proposal for showing thousand separator in form controls.

On 10/15/15 2:35 AM, Михаил Гаврилов wrote: Let's first decide what numbers is meant by number type. Good luck with that. Everyone seems to feel it's a different thing. Also a special case is the number of a credit card and any number with leading zero. Because leading zero no have

Re: [whatwg] Proposal for showing thousand separator in form controls.

On Thu, 15 Oct 2015, Михаил Гаврилов wrote: > > Frankly I do not understand it means, yes or no? > I am first time here. > How did approval procedure takes place? > Anything else I need to do or describe final idea? Any examples how > make this better. You may find more details about how things

Re: [whatwg] Proposal for showing thousand separator in form controls.

Frankly I do not understand it means, yes or no? I am first time here. How did approval procedure takes place? Anything else I need to do or describe final idea? Any examples how make this better. Thanks. -- Best Regards, Mike Gavrilov. 2015-10-15 20:30 GMT+05:00 Boris Zbarsky

Re: [whatwg] Proposal for showing thousand separator in form controls.

2015-10-14 0:41 GMT+05:00 Boris Zbarsky : > See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. I think the problem with the display of the year with the help of far-fetched. Sooner or later year will be five-digit and more, and 85321 year will be better to

Re: [whatwg] Proposal for showing thousand separator in form controls.

On 14 October 2015 10:47:43 BST, "Михаил Гаврилов" wrote: >2015-10-14 0:41 GMT+05:00 Boris Zbarsky : >> See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. > >I think the problem with the display of the year with the help of >

Re: [whatwg] Proposal for showing thousand separator in form controls.

On 10/14/15 5:47 AM, Михаил Гаврилов wrote: 2015-10-14 0:41 GMT+05:00 Boris Zbarsky : See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. I think the problem with the display of the year with the help of far-fetched. In what sense? People are doing it

[whatwg] Proposal for showing thousand separator in form controls.

Hi to all! Excuse me I am newbie here. I want make a proposal for displaying thousand separator in numeric input fields. Most users would be more satisfied if in any would seen as 1 234 567 890.012 345 678 9 of course thousand separator must depend of local settings. 1234567890.0123456789 =

Re: [whatwg] Proposal for showing thousand separator in form controls.

On 10/13/15 3:35 PM, Domenic Denicola wrote: S ... any implementers interested in solving this problem? Note that Gecko used to show such separators, then stopped doing that. See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. It might be worth having some way to opt in

Re: [whatwg] Proposal for showing thousand separator in form controls.

On Tue, Oct 13, 2015 at 12:35 PM, Domenic Denicola wrote: > especially since custom elements are unable to participate in the form > control ecosystem That is very fixable though. There have been good proposals made. / Jonas

Re: [whatwg] Proposal for showing thousand separator in form controls.

This has come up before; I think https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Feb/0075.html is the most recent thread on the subject. In general, the spec does not mandate such UI features of browsers, but the input types are somewhat of a gray area in that regard, since part

Re: [whatwg] Persistent state for homescreen web apps (without reloading each time)

hat when the OS switches back to it it will do a reload, just >> like when I switch back to my mail app it does a sync, and other stuff like >> that. >> >> > -Original Message- >> > From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Zac &g

Re: [whatwg] Unicode -> ASCII copy/paste fallback

David Sheets writes: > On Sun, Feb 15, 2015 at 3:16 AM, Glenn Maynard wrote: >> On Sat, Feb 14, 2015 at 12:34 PM, David Sheets wrote: >>> >>> I am writing a documentation generation tool for a programming >>> language with right arrows

Re: [whatwg] Persistent state for homescreen web apps (without reloading each time)

> On Jun 9, 2015, at 3:55 PM, Zac Spitzer wrote: > > But what do end users or developers expect in terms of browser behavior in > this situation? > > The history api (or saving state to indexedDB) aren't going to solve the > problem of reinitialization everytime the user

Re: [whatwg] : Issue reported by the web developers

el attribute be honored if specified, otherwise use the textContent with leading and trailing whitespace trimmed. This would allow either syntax unless I'm missing something. File an issue on doing this? Filed https://github.com/whatwg/html/issues/234 and https://github.com/whatwg/htm

Re: [whatwg] : Issue reported by the web developers

On Wed, Nov 26, 2014 at 9:50 AM, Simon Pieters wrote: > Make the end tag optional and have , and generate > implied end tags. (Maybe other tags like and can also > imply .) The label attribute be honored if specified, otherwise > use the textContent with leading and

Re: [whatwg] : Issue reported by the web developers

So, here's one example of a page putting content inside of : https://developer.apple.com/library/prerelease/ios/documentation/HealthKit/Reference/HealthKit_Constants/index.html#//apple_ref/c/econst/HKBodyTemperatureSensorLocationRectum If you use Chrome with the Experimental Web Platform Features

Re: [whatwg] Removing mediagroup/MediaController from HTML

On Fri, Oct 2, 2015 at 10:27 AM, Domenic Denicola <d...@domenic.me> wrote: > From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of > >> is removal really the right thing to do, given that we have an >> implementation? > > I agree this is a problemat

Re: [whatwg] Removing mediagroup/MediaController from HTML

> On Oct 1, 2015, at 6:49 , Anne van Kesteren <ann...@annevk.nl> wrote: > > In https://github.com/whatwg/html/issues/192 we're planning on > removing mediagroup/MediaController from HTML since other than WebKit > no implementations appear interested in implementin

Re: [whatwg] Removing mediagroup/MediaController from HTML

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of > is removal really the right thing to do, given that we have an > implementation? I agree this is a problematic question. I opened https://github.com/whatwg/html/issues/209 for the more general issue but am happy t

[whatwg] XML/HTML Entities draft

Ian, Not sure if you still use a "live" copy of unicode.xml and hopefully there will never be a need to change the HTML character entity definitions but anyway The editor's draft of the entities spec has been moved to github https://w3c.github.io/xml-entities/ (The old URL at

Re: [whatwg] XML/HTML Entities draft

On Fri, 2 Oct 2015, David Carlisle wrote: > > Ian, > Not sure if you still use a "live" copy of unicode.xml > and hopefully there will never be a need to change the > HTML character entity definitions but anyway > > > The editor's draft of the entities spec has been moved to github > > > >

[whatwg] Removing mediagroup/MediaController from HTML

In https://github.com/whatwg/html/issues/192 we're planning on removing mediagroup/MediaController from HTML since other than WebKit no implementations appear interested in implementing these features. -- https://annevankesteren.nl/

Re: [whatwg] `iframe[@sandbox]`: "sandblaster" JS library for analysis/modification

On Wed, Sep 30, 2015 at 10:51 AM, Mike West wrote: > On Wed, Sep 30, 2015 at 4:56 PM, James M. Greene > wrote: >> >> *and* potentially modifying/dismantling >> iframe sandboxes. >> > > Are you able to do this in any cases other than

[whatwg] `iframe[@sandbox]`: "sandblaster" JS library for analysis/modification

*I should've shared this a long time ago but better late than never* Last winter, I was dealing with some confusion surrounding `iframe` sandboxing [when I wasn't aware it existed] on code playground sites (JSFiddle, JSBin, CodePen, etc.). While investigating, I ended up creating a JS

Re: [whatwg] `iframe[@sandbox]`: "sandblaster" JS library for analysis/modification

On Wed, Sep 30, 2015 at 4:56 PM, James M. Greene wrote: > While investigating, I ended up creating a JS library called *sandblaster* > [1] to assist me in analyzing We should probably just provide a mechanism for reading the currently active sandboxing flags. You

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

k you Allen. It would then make the most sense to rethrow that > exception for these methods (and ImageData constructor). I > filed https://github.com/whatwg/html/issues/197 to track this. If > anyone is interested in working on this let me know. It should be a > relatively straightforwa

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

capabilities to follow that same pattern. > > [1]: http://ecma-international.org/ecma-262/6.0/#sec-createbytedatablock Thank you Allen. It would then make the most sense to rethrow that exception for these methods (and ImageData constructor). I filed https://github.com/whatwg/html/issues/197

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

On Sat, Sep 26, 2015 at 7:34 AM, Anne van Kesteren wrote: > On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad wrote: > > Currently there is no spec'ed behavior for handling out-of memory issues > > for the specific case of attempting to allocate a large buffer

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

ich point the user is generally screwed anyway if > he didn't patch in time. Being able to detect a vulnerability is not a > prerequisite for exploiting it. > > Niels > > -Original Message- > From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Anne >

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

Since my post is about the more general OOM issue, I have shifted the discussion to es-discuss https://mail.mozilla.org/pipermail/es-discuss/2015-September/044267.html Please continue discussion of the non-browser-specific issue there. On Sun, Sep 27, 2015 at 8:33 AM, Mark S. Miller

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

On Sep 26, 2015, at 7:34 AM, Anne van Kesteren wrote: > On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad wrote: >> Currently there is no spec'ed behavior for handling out-of memory issues >> for the specific case of attempting to allocate a large buffer through >> image data

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

I should make it clear that my post is not concerned about OOM for image data -- the original subject of this thread -- but rather about the more general OOM question that Anne asks about. On Sat, Sep 26, 2015 at 9:15 PM, Rik Cabanier wrote: > On Fri, Sep 25, 2015 at 7:51

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

On Sun, Sep 27, 2015 at 8:30 AM, Mark S. Miller wrote: > On Sat, Sep 26, 2015 at 7:34 AM, Anne van Kesteren > wrote: > >> On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad wrote: >> > Currently there is no spec'ed behavior for handling

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

omised, at which point the user is generally screwed anyway if he didn't patch in time. Being able to detect a vulnerability is not a prerequisite for exploiting it. Niels -Original Message- From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Anne van Kesteren Sent: zater

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

On Fri, Sep 25, 2015 at 7:51 AM, Boris Zbarsky wrote: > On 9/25/15 10:48 AM, Justin Novosad wrote: > >> I am sharing this here in case there would be interest in standardizing >> this behavior. >> > > I personally think it's a good idea (and throwing an exception is how > Gecko

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

On Fri, Sep 25, 2015 at 4:48 PM, Justin Novosad wrote: > Currently there is no spec'ed behavior for handling out-of memory issues > for the specific case of attempting to allocate a large buffer through > image data APIs. Actually, there is no specified behavior for

[whatwg] Handling out of memory issues with getImageData/createImageData

Hi All, Currently there is no spec'ed behavior for handling out-of memory issues for the specific case of attempting to allocate a large buffer through image data APIs. In Chrome, the current behavior is to crash the process (out of memory exception), which results in a "sad browser tab". We

Re: [whatwg] Handling out of memory issues with getImageData/createImageData

On 9/25/15 10:48 AM, Justin Novosad wrote: I am sharing this here in case there would be interest in standardizing this behavior. I personally think it's a good idea (and throwing an exception is how Gecko handles, or at least aims to handle, this situation). -Boris

Re: [whatwg] Icon mask and theme color

;> Use the following markup instead: >> This is now https://github.com/whatwg/html/issues/110. -- https://annevankesteren.nl/

Re: [whatwg] Icon mask and theme color

Followup on this. Le 16 juin 2015 à 02:33, Edward O'Connor a écrit : > That is why we recommend authors put rel=icon mask> first—so that the existing tie-breaking behavior results > in the legacy favicon being chosen. Nicolas Hoizey spotted on Apple forums and added a

Re: [whatwg] W3C Timed Text Working Group proposal for HTMLCue

Hi Nigel, I'm trying to spend less time on WebVTT and related questions these days, but here's my high-level feedback, inline: On Thu, Sep 10, 2015 at 11:46 PM, Nigel Megitt <nigel.meg...@bbc.co.uk> wrote: > Dear WhatWG, Jer, Eric, Silvia, Philip, > > W3C Timed Text Working Group

[whatwg] W3C Timed Text Working Group proposal for HTMLCue

[Resending after subscribing to WHATWG list - apologies for the noise] Dear WhatWG, Jer, Eric, Silvia, Philip, W3C Timed Text Working Group kindly requests you to consider the following proposal: - What? - We propose to specify an implementation

Re: [whatwg] W3C Timed Text Working Group proposal for HTMLCue

On Thu, 10 Sep 2015, Nigel Megitt wrote: > >On Thu, 10 Sep 2015, Nigel Megitt wrote: > >> > >> We think an HTML cue as a variant of the third option is the best > >> solution. > > > >If you do this please make sure to define in detail how it should all > >work. > > Are you commenting that it

Re: [whatwg] W3C Timed Text Working Group proposal for HTMLCue

(Please don't cross-post to the WHATWG list -- either post to the WHATWG list, or post to other lists, but not both at the same time. It causes threads to fragment as people aren't on all the lists.) On Thu, 10 Sep 2015, Nigel Megitt wrote: > > We think an HTML cue as a variant of the

Re: [whatwg] W3C Timed Text Working Group proposal for HTMLCue

On 11/09/2015 00:11, "Ian Hickson" <i...@hixie.ch> wrote: >(Please don't cross-post to the WHATWG list -- either post to the WHATWG >list, or post to other lists, but not both at the same time. It causes >threads to fragment as people aren't on all the lists.)

[whatwg] [CSSWG][css-cascade-4] Last Call for Comments on CSS Cascading and Inheritance Level 4

The CSS WG has published an updated Working Draft of the CSS Cascading and Inheritance Module Level 4 http://www.w3.org/TR/css-cascade-4/ This CSS module describes how to collate style rules and assign values to all properties on all elements by way of cascading (choosing a winning

[whatwg] New ruby elements in HTML

com/whatwg/html/pull/101 provides my recommended solution. It's less clear to me we should be changing anything else. -- https://annevankesteren.nl/

Re: [whatwg] deprecating

d. I'm really not trying to do that specifically. This thread just keeps accidentally entering into the kinds of areas that we try to keep off the WHATWG list, to wit, non-technical arguments, arguments about other groups' specifications, arguments about implementors' plans and motives, d

Re: [whatwg] deprecating

re are replacement APIs being developed. I'm not personally familiar with that work so I can't comment on it. Should the authors of a cryptography specification that browser vendors want to implement be interested in publishing their work through the WHATWG, I'm sure that could be arranged, and a

Re: [whatwg] How to add html5 browser support

On Thu, Sep 3, 2015 at 10:45 AM, Brian Jones wrote: > I'm taking online class to program a browser from scratch. How do I > add Html5 support? Thank you. -Brian Jones You read the spec and then implement all of it. Mind you, it might

Re: [whatwg] deprecating

where discussions making explicit the reasons for this ( and other ) decision can be made, so that the larger community of users of the technologies the browser vendors are implementing can have a voice, and also like in any open source project to have a lot of different eyes help work through the tan

Re: [whatwg] deprecating

On Thu, 3 Sep 2015, Melvin Carvalho wrote: > > > > The post foolip pointed to points out that is actually rather > > insecure (e.g. using MD5). One could argue that _keeping_ is > > actually more harmful to asymetric-key cryptography than removing > > it... > > Im not an expert here, but my

Re: [whatwg] deprecating

licit the reasons for this ( and other ) decision can be made, so > that the larger community of users of the technologies the browser > vendors are implementing can have a voice, and also like in any open > source project to have a lot of different eyes help work through the > tangle of compl

Re: [whatwg] deprecating

> On Sep 3, 2015, at 11:33 AM, Melvin Carvalho wrote: >> > > Im not an expert here, but my understanding from reading some wikipedia > articles was that a preimage attack on md5 was 2^123. For a pre-image attack that’s true (or thereabouts), the real problem is

Re: [whatwg] deprecating

iar with that work so I can't > comment on it. Should the authors of a cryptography specification that > browser vendors want to implement be interested in publishing their work > through the WHATWG, I'm sure that could be arranged, and at that point > this list would make for a v

Re: [whatwg] deprecating

On 3 September 2015 at 21:27, Ian Hickson wrote: > On Thu, 3 Sep 2015, Melvin Carvalho wrote: > > > > > > The post foolip pointed to points out that is actually rather > > > insecure (e.g. using MD5). One could argue that _keeping_ is > > > actually more harmful to asymetric-key

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