Re: [whatwg] [proposal] Gallery element

Thanks for the reply Jonathan. > Jonathan Zuckerman hat am 13. Juli 2016 um 14:36 > geschrieben: > > Hi Hans, I'm not an important figure at all in the web world, but my > intuition is this isn't a good candidate for a new feature in HTML. You've > done a good job of abstracting the problem and

Re: [whatwg] [proposal] Gallery element

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Hans Schmucker > Right now this is little more than a description of a problem with a rough > outline how a solution could work, so there are obviously a lot of issues not > discussed in this proposal. What I'd l

Re: [whatwg] [proposal] Gallery element

Hi Hans, I'm not an important figure at all in the web world, but my intuition is this isn't a good candidate for a new feature in HTML. You've done a good job of abstracting the problem and exploring the edge cases but the feature is just too specific. I doubt browser vendors would want to implem

[whatwg] [proposal] Gallery element

Note: I've already sent this to the W3C public-html list, and while there hasn't been any response so far, it is possible that issues will be raised on both channels. The original message along with replies is available at http://lists.w3.org/Archives/Public/public-html/2016Jul/0011.html . Although

Re: [whatwg] Proposal: User-Cacheable Media

On Fri, Jul 1, 2016 at 1:43 PM, wrote: > Hello Everyone! > > I would like to propose what I think would be a new feature for HTML AV > playback. Thanks to the great work everyone on this list has done, web > authors now have several solid tools for caching webpages and their > content for offline

[whatwg] Proposal: User-Cacheable Media

Hello Everyone! I would like to propose what I think would be a new feature for HTML AV playback. Thanks to the great work everyone on this list has done, web authors now have several solid tools for caching webpages and their content for offline access. I think what is missing today is the abilit

Re: [whatwg] Multimedia quality conformance

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Satyanarayana N > Is there any provision available for checking the quality of media elements > such as audio/video/image before sending it to remote server in web audio > API or getUserMedia API or pasting it on canva

[whatwg] Multimedia quality conformance

Hi, Is there any provision available for checking the quality of media elements such as audio/video/image before sending it to remote server in web audio API or getUserMedia API or pasting it on canvas element. Scenario: Now web is being used as a tool in social networking/educational sites and

Re: [whatwg] [CSSWG][css-content] FPWD of CSS Generated Content L3

On 06/20/2016 06:14 PM, Phillips, Addison wrote: +I18N Core Thanks for this. I have added this to I18N's radar [1]. Do you have a due date for comments in mind? Or a general schedule? Not really. ~fantasai

[whatwg] [CSSWG][css-content] FPWD of CSS Generated Content L3

Okay, so it's *technically* not a FPWD, but since it's a near-complete rewrite of the 2003 draft, I'm announcing it as one, since it warrants that level of review. :) The CSS WG has published an updated Working Draft of the CSS Generated and Replaced Content Module Level 3: https://www.w3.or

[whatwg] [CSSWG][css-pseudo-4] Updated WD of CSS Pseudo-elements Level 4

The CSS WG has published an updated Working Draft of the CSS Pseudo-elements Module Level 4: https://www.w3.org/TR/css-pseudo-4/ This CSS module defines pseudo-elements, abstract elements that represent portions of the CSS render tree that can be selected and styled. This somewhat-overdue pub

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Geoffrey Garen > Should navigator.language and/or HTTP Accept-Language include my locale in > addition to my language — even if the combination is exotic? It seems like there was a good discussion on this thread but not m

Re: [whatwg] Proposal: element

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of David Kendal > I would like to propose a new element for the HTML standard, . Hi David; have you read https://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F ? In particular, it

[whatwg] Proposal: element

I would like to propose a new element for the HTML standard, . The element is a phrasing element representing a label or tag. Semantically, it attaches the label to the nearest enclosing , , , , , or to the entire document if there is no such enclosing element. Example uses for the proposed elem

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

. Sites should not change the locale that the user has chosen for himself. There is a proposal to do that at https://github.com/whatwg/html/issues/171 but it has not meaningfully progressed thus far. Note also that some sites go out of their way to localize form controls to fit the language of the site

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

that the user has chosen >> for himself. > > There is a proposal to do that at > https://github.com/whatwg/html/issues/171 but it has not meaningfully > progressed thus far. > > Note also that some sites go out of their way to localize form > controls to fit the language o

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

proposal to do that at https://github.com/whatwg/html/issues/171 but it has not meaningfully progressed thus far. Note also that some sites go out of their way to localize form controls to fit the language of the site. To the extent they will use libraries rather than and friends. Arguably they&#

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

I propose to standardize locale settings (datetime, number delimeters) can be specified only by user via the operating system settings. Sites should not change the locale that the user has chosen for himself. -- Best Regards, Mike Gavrilov. 2016-05-25 10:15 GMT+05:00 Anne van Kesteren : > On We

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

On Wed, May 25, 2016 at 4:50 AM, Geoffrey Garen wrote: > My claim is that if you want English language with Russian regional settings > then browsers must report “en-ru” in navigator.language. That doesn't work. What if you want British English and the Russian locale? Or Canadian French with the

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

> I'm afraid that bind regional setting to interface language is not > correct. For example, I prefer the English language interface (it's > easier to write bug reports, search in Google documentation), but I > need the russian regional settings (number format, date format and > time format) for in

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

>> This question came up in WebKit because ECMA-402’s DefaultLocale() >> incorporates both language and locale and, to avoid confusion, we >> wanted navigator.language, HTTP Accept-Language, and ECMA-402 >> DefaultLocale() to agree with each other. > > It confuses me why you would want to have tho

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

I'm afraid that bind regional setting to interface language is not correct. For example, I prefer the English language interface (it's easier to write bug reports, search in Google documentation), but I need the russian regional settings (number format, date format and time format) for input contro

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

On Tue, May 24, 2016 at 1:55 AM, Nils Dagsson Moskopp wrote: > • navigator.language is the language of the interface > • HTTP Accept-Language is the language of content > • ECMA-402 DefaultLocale() is the user's locale The HTML Standard has a should-level requirement for the first two to align, t

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

On Mon, May 23, 2016 at 11:58 PM, Geoffrey Garen wrote: > For example, if I speak English but I like Polish number formatting, should > navigator.language report “en-pl”? I don't think so. That would only make sense if English was a language spoken in Poland that differs from other English langu

Re: [whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

Geoffrey Garen writes: > Hi folks. > > Should navigator.language and/or HTTP Accept-Language include my > locale in addition to my language — even if the combination is exotic? > > For example, if I speak English but I like Polish number formatting, > should navigator.language report “en-pl”? > >

[whatwg] Should navigator.language and and/or HTTP Accept-Language include locale?

Hi folks. Should navigator.language and/or HTTP Accept-Language include my locale in addition to my language — even if the combination is exotic? For example, if I speak English but I like Polish number formatting, should navigator.language report “en-pl”? This question came up in WebKit becau

[whatwg] Fw: new message

Hello! You have a new message, please read <http://yourdentalfirst.com.previewdns.com/support.php?gkp5j> whatwg

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On May 1, 2016 1:08 PM, "Rik Cabanier" wrote: > > Great to hear! > Are there minutes posted? As far as I know, the minutes and mail archives are visible to members only. I'm working to capture what we have so far and to move the discussion to a broader and more visible forum. > > > On Sunday, May

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

Great to hear! Are there minutes posted? On Sunday, May 1, 2016, Justin Novosad wrote: > There is currently an ongoing discussion with the Khronos Web3D group to > develop a proposal that solves these problems in canvas, over the past few > weeks we have converged on a solution that I think is p

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

There is currently an ongoing discussion with the Khronos Web3D group to develop a proposal that solves these problems in canvas, over the past few weeks we have converged on a solution that I think is pretty solid. I am in the process of writing-up the HTML (non-WebGL) part of the proposal and I i

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 6:35 PM, Ron Waldon wrote: > What if we could just declare the colour-space that content uses, and > allow the browser to make a best-effort translation if the current display > uses a different colour-space? > That is pretty much the situation in Safari today. My origina

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

What if we could just declare the colour-space that content uses, and allow the browser to make a best-effort translation if the current display uses a different colour-space? This way, we don't need to expose colour profiles or other fingerprinting details to JavaScript code. That code can just d

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 4:27 PM, Rik Cabanier wrote: > > > On Sat, Apr 30, 2016 at 3:25 PM, Kornel wrote: > >> >> On 30 Apr 2016, at 21:19, Rik Cabanier wrote: >> >>> >>> > It would be ideal if we can specify that the canvas backing store is >>> in the device profile. >>> >>> How would the webs

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 3:25 PM, Kornel wrote: > > On 30 Apr 2016, at 21:19, Rik Cabanier wrote: > >> >> > It would be ideal if we can specify that the canvas backing store is in >> the device profile. >> >> How would the website know what profile this is? If it's just a boolean >> setting, then

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

> On 30 Apr 2016, at 21:19, Rik Cabanier wrote: > > > It would be ideal if we can specify that the canvas backing store is in the > > device profile. > > How would the website know what profile this is? If it's just a boolean > setting, then I don't see how it would make it possible to use su

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

On Sat, Apr 30, 2016 at 12:38 PM, Kornel wrote: > > > On 30 Apr 2016, at 19:07, Rik Cabanier wrote: > > > > It would be ideal if we can specify that the canvas backing store is in > the device profile. > > How would the website know what profile this is? If it's just a boolean > setting, then I

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

> On 30 Apr 2016, at 19:07, Rik Cabanier wrote: > > It would be ideal if we can specify that the canvas backing store is in the > device profile. How would the website know what profile this is? If it's just a boolean setting, then I don't see how it would make it possible to use such canvas

Re: [whatwg] Canvas and color colorspaces (was: WebGL and ImageBitmaps)

[Sorry to revive this old thread] All, with the advent of DCI-P3 compliant monitors and Apple's Safari doing color managing to the device, we're seeing some issues in this area. - Currently, WebKit sets the profile of the canvas backing store to sRGB regardless of the output device. Because of th

Re: [whatwg] VIDEO and pitchAdjustment

On Fri, Mar 11, 2016 at 1:19 PM, Jer Noble wrote: > > On Mar 11, 2016, at 1:11 PM, Garrett Smith wrote: > … > I also found:— > https://developer.apple.com/library/prerelease/ios/documentation/AVFoundation/Reference/AVAudioUnitTimePitch_Class/ > ("preliminary document for an API or technology in

[whatwg] Fw: new important message

Hello! New message, please read <http://getsport.pro/economics.php?8> whatwg

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 15, 2016, at 1:58 PM, Arvind Nigam wrote: > > On mobile the browser goes totally unresponsive and the infinite-loop of > modal confirmations is literally inescapable. I’ll drop this thread after this, but what I wanted to say is this: This extremely bad experience described here is a

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 15, 2016, at 1:58 PM, Arvind Nigam wrote: > > While I understand your inclination towards Apple Safari, it is out of > question that people won't use other browsers like the Chrome or Firefox or > even the UC browser to surf the web. The problem you complained about is fixed in the b

Re: [whatwg] JavaScript dialogs blocking user experience

> It’s too bad you were using the UC browser. If you had been using > Safari you would not have been trapped by the scam. If you continue to > prefer the UC browser over Safari then you should consider how to let > the developers know you would like to see this improved. Oh, I love the Safari, bu

Re: [whatwg] JavaScript dialogs blocking user experience

Darin Adler writes: >> On Apr 15, 2016, at 9:35 AM, Nils Dagsson Moskopp >> wrote: >> >> Clearly distinguishing between browser chrome and the current document >> interface-wise can be helpful here. While it is incredibly easy to fool >> people in general, browsers that automagically hide the

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 15, 2016, at 9:35 AM, Nils Dagsson Moskopp > wrote: > > Clearly distinguishing between browser chrome and the current document > interface-wise can be helpful here. While it is incredibly easy to fool > people in general, browsers that automagically hide the address bar also > hide info

Re: [whatwg] JavaScript dialogs blocking user experience

Darin Adler writes: >> On Apr 14, 2016, at 2:17 PM, Arvind Nigam wrote: >> >> My iPad is on iOS 9.3.1, but I was using the UC browser at the time. > > It’s too bad you were using the UC browser. If you had been using > Safari you would not have been trapped by the scam. If you continue to > pre

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 14, 2016, at 2:17 PM, Arvind Nigam wrote: > > My iPad is on iOS 9.3.1, but I was using the UC browser at the time. It’s too bad you were using the UC browser. If you had been using Safari you would not have been trapped by the scam. If you continue to prefer the UC browser over Safari

Re: [whatwg] JavaScript dialogs blocking user experience

flexible, we're certainly open to > that, in the same spirit as the semi-recent > https://github.com/whatwg/html/pull/714. > > Here are two things we might want to address in the specification—not sure > either is practical: > > - Find some place to emphasize the importanc

Re: [whatwg] JavaScript dialogs blocking user experience

ptionally" in step 7. If any browser has qualms with the current > language and would like it to be more flexible, we're certainly open to that, > in the same spirit as the semi-recent https://github.com/whatwg/html/pull/714. Here are two things we might want to address in the specific

Re: [whatwg] JavaScript dialogs blocking user experience

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of > The problem you describe above was addressed by Apple in iOS 9.3 and also > in Safari 9.1 on Mac. That release changed the style of JavaScript alerts so > that they are less likely to appear to come from Safari, the

Re: [whatwg] JavaScript Hovers and Back Button

> On Apr 14, 2016, at 10:38 AM, Arvind Nigam wrote: > > I wish to add that this issue is a bit more annoying on mobile: both on > iPad and iPhone. > > Once the webpage loads, it goes into a JS invoked confirm/ok modal that > would not relent -- not without seeking credit card info or something e

Re: [whatwg] JavaScript Hovers and Back Button

Hi, Unlike others on this thread I'm a little more ordinary user of the web. Came across one such modal just today! So thank you for reporting this. I wish to add that this issue is a bit more annoying on mobile: both on iPad and iPhone. I guess the behavior on Android phones too will also be th

Re: [whatwg] JavaScript Hovers and Back Button

*Windows* IE11, Chrome: Navigation buttons are blocked while modal dialog is shown. Firefox: Navigation buttons remain usable. On Thu, Apr 14, 2016 at 8:34 AM, Majid Valipour wrote: > > A very common abuse is that when pulling the mouse to hit the back > > button because you are not interested i

Re: [whatwg] JavaScript Hovers and Back Button

> A very common abuse is that when pulling the mouse to hit the back > button because you are not interested in a page, a hover comes up and > when the hover comes up, the back button no longer works. Does 'hover' refer to modal dialog e.g., window.alert? That is the only way I know that you can b

Re: [whatwg] JavaScript Hovers and Back Button

Agree. May it be done within the History API spec? Just wondering. --- 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 2016-04-13 21:

Re: [whatwg] JavaScript Hovers and Back Button

Last one I found is already taken down (I always report it to the ISP - often Amazon cloud) What it does is make loud buzzing noises while flashing a message that your computer has been infected with a virus and you must call microsoft support immediately. Only thing that works is closing th

Re: [whatwg] JavaScript Hovers and Back Button

I have heard of a lot of abuses but never actually come across this particular one, can you point us to a site that demonstrates it? On Wed, Apr 13, 2016 at 3:53 PM, Michael A. Peters wrote: > This btw is a security issue. Many of the scam sites that do things like > tell the user their computer

Re: [whatwg] JavaScript Hovers and Back Button

This btw is a security issue. Many of the scam sites that do things like tell the user their computer is infected and they have to call a number disable the ability to use the back button via JavaScript hovers. This puts users who don't understand technology into a mental state where they feel

[whatwg] JavaScript Hovers and Back Button

It needs to be made very clear as a web standard that no JavaScript action can disable UI functions such as the back button. A very common abuse is that when pulling the mouse to hit the back button because you are not interested in a page, a hover comes up and when the hover comes up, the bac

Re: [whatwg] Document with a single input[type=radio]?

Mikko Rantalainen writes: > The spec says in 4.10.5.1.16 Radio Button state (type=radio) > https://html.spec.whatwg.org/multipage/forms.html#radio-button-state-%28type=radio%29 > > "A document must not contain an input element whose radio button group > contains only that element." > > What this

Re: [whatwg] Document with a single input[type=radio]?

On Thu, Apr 7, 2016 at 2:48 PM, Mikko Rantalainen < mikko.rantalai...@peda.net> wrote: > The spec says in 4.10.5.1.16 Radio Button state (type=radio) > > > > https://html.spec.whatwg.org/multipage/forms.html#radio-button-state-%28type=radio%29 > > "A document must not contain an input element whos

Re: [whatwg] Document with a single input[type=radio]?

This is an authoring requirement, not a browser implementation requirement. In practice, it means conformance checkers (aka validators) should error for lone radio buttons. From: Mikko Rantalainen Sent: Apr 7, 2016 7:49 AM To: whatwg@lists.whatwg.org Subject: [whatwg] Document with a single

[whatwg] Document with a single input[type=radio]?

The spec says in 4.10.5.1.16 Radio Button state (type=radio) https://html.spec.whatwg.org/multipage/forms.html#radio-button-state-%28type=radio%29 "A document must not contain an input element whose radio button group contains only that element." What this is supposed to mean in practice? Could

Re: [whatwg] Expose the 'renderport' to content

On Tue, Apr 5, 2016 at 10:26 PM, Matt Woodrow wrote: > Our suggested solution to this is to add a callback to scrollable elements > that fires before painting (similar to requestAnimationFrame) and exposes > the (approximate) region of the element that the UA is going to treat as > visible for the

[whatwg] Expose the 'renderport' to content

Hi, I'd like to propose exposing the 'renderport' to web content, defined as the area of a scrollable container that is actually rendered by the UA, which may be larger than the viewport (visible) area. Most browsers these days are rendering areas larger than what is currently visible (espec

Re: [whatwg] New tag

On Fri, Apr 1, 2016 at 5:55 PM, Karl Dubost wrote: > > Le 2 avr. 2016 à 04:04, Daniel Murphy a écrit : > > we wouldn't want to waste our expensive > > smell synthesis technology on the likes of webcrawlers and other robots > who > > wouldn't benefit. > > > Yup. User agent sniffing definitely sti

Re: [whatwg] New tag

Le 2 avr. 2016 à 04:04, Daniel Murphy a écrit : > we wouldn't want to waste our expensive > smell synthesis technology on the likes of webcrawlers and other robots who > wouldn't benefit. Yup. User agent sniffing definitely stinks. -- Karl Dubost 🐄 http://www.la-grange.net/karl/

Re: [whatwg] We need more colors in CSS

Not really, Alex. We have more colours now through _SYNAESTHESIA_, thanks to the tag ;) --- 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]

[whatwg] We need more colors in CSS

I read today's thread about and I disagree - we have a higher priority to deal with. We really need to replace RGB with RGBU: red, green, blue, ultraviolet. After all, some people have cones in their eyes to detect ultraviolet light. I believe the technical term is "tetrachromacy", or something

Re: [whatwg] New tag

We need the detection api because we wouldn't want to waste our expensive smell synthesis technology on the likes of webcrawlers and other robots who wouldn't benefit. On Fri, Apr 1, 2016 at 12:01 PM Daniel Murphy wrote: > Don't forget, we also need: > > *SmellEvent* > >- "onsmellchanged" >

Re: [whatwg] New tag

Don't forget, we also need: *SmellEvent* - "onsmellchanged" - "onsmellstart" - "onsmellend" - "ongoodsmell" - "onbadsmell" And the new detection api: window.doesUserHaveNose() : Promise On Fri, Apr 1, 2016 at 11:14 AM Delfi Ramirez wrote: > Garrett et al: > > I really apprecia

Re: [whatwg] New tag

Just a lighthearted April Fools, and that's it. Sorry if it made anyone upset. Sent from my bathroom Attachment: poo.sm > On Apr 1, 2016, at 11:14 AM, Delfi Ramirez wrote: > > Garrett et al: > > I really appreciate your delicate sense of humour. Not sure if all the > people in the list do

Re: [whatwg] New tag

Garrett et al: I really appreciate your delicate sense of humour. Not sure if all the people in the list does the same. We all know a computer-- opossite to we human beings - is unable to interpret correctly, unconciently, the information pheromones and smells have. I am speaking now like t

[whatwg] New tag

There has been good progress in HTML5 for and . But the tag has been missing — why? Well no longer, now thanks to a new game-changing proposal: But it occurred to me: This could be huge paradigm shift in towards Internet Odorous Things. boolean `navigator.isSmellEnabled` Thank you, -- Gar

Re: [whatwg] VIDEO and pitchAdjustment

On Fri, Mar 11, 2016 at 1:19 PM, Jer Noble wrote: > > On Mar 11, 2016, at 1:11 PM, Garrett Smith wrote: > > > > On Tuesday, March 8, 2016, Jer Noble wrote: >> >> >> > On Mar 8, 2016, at 4:42 PM, Garrett Smith >> > wrote: >> > >> > On Fri, Mar 4, 2016 at 3:43 PM, Jer Noble wrote: >> >> >> >>> O

Re: [whatwg] VIDEO and pitchAdjustment

Hi, O Ven, 11-03-2016 ás 13:19 -0800, Jer Noble escribiu: > > Oh. Poor hardware integration, and now this…. Being Apple CEO is > not Tim Cook's greatest gift…  > > I’m not sure how that’s relevant. Yes I agree with Jer here, it looks like a very bad, undesired and irrelevant joke. Best

Re: [whatwg] VIDEO and pitchAdjustment

> On Mar 11, 2016, at 1:11 PM, Garrett Smith wrote: > > > > On Tuesday, March 8, 2016, Jer Noble > wrote: > > > On Mar 8, 2016, at 4:42 PM, Garrett Smith > wrote: > > > > On Fri, Mar 4, 2016 at 3:43 PM, Jer Noble > wrote: > >> > >>> On Mar 4, 2016, at 3:19 PM, Gar

Re: [whatwg] VIDEO and pitchAdjustment

On Tuesday, March 8, 2016, Jer Noble wrote: > > > On Mar 8, 2016, at 4:42 PM, Garrett Smith > wrote: > > > > On Fri, Mar 4, 2016 at 3:43 PM, Jer Noble wrote: > >> > >>> On Mar 4, 2016, at 3:19 PM, Garrett Smith > wrote: > >>> > >>> On Fri, Mar 4, 2016 at 1:55 PM, Jer Noble wrote: > > >>>

Re: [whatwg] VIDEO and pitchAdjustment

On Fri, Mar 4, 2016 at 3:43 PM, Jer Noble wrote: > >> On Mar 4, 2016, at 3:19 PM, Garrett Smith wrote: >> >> On Fri, Mar 4, 2016 at 1:55 PM, Jer Noble wrote: >>> On Mar 1, 2016, at 8:00 PM, Philip Jägenstedt wrote: On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith wrote: >

Re: [whatwg] VIDEO and pitchAdjustment

> On Mar 4, 2016, at 3:19 PM, Garrett Smith wrote: > > On Fri, Mar 4, 2016 at 1:55 PM, Jer Noble wrote: >> >>> On Mar 1, 2016, at 8:00 PM, Philip Jägenstedt wrote: >>> >>> On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith >>> wrote: On Thu, Nov 12, 2015 at 11:32 AM, Philip Jägenstedt >>

Re: [whatwg] VIDEO and pitchAdjustment

On Fri, Mar 4, 2016 at 1:55 PM, Jer Noble wrote: > >> On Mar 1, 2016, at 8:00 PM, Philip Jägenstedt wrote: >> >> On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith wrote: >>> On Thu, Nov 12, 2015 at 11:32 AM, Philip Jägenstedt >>> wrote: On Thu, Nov 12, 2015 at 10:55 AM, Garrett Smith wr

Re: [whatwg] VIDEO and pitchAdjustment

> On Mar 1, 2016, at 8:00 PM, Philip Jägenstedt wrote: > > On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith wrote: >> On Thu, Nov 12, 2015 at 11:32 AM, Philip Jägenstedt >> wrote: >>> On Thu, Nov 12, 2015 at 10:55 AM, Garrett Smith >>> wrote: On 11/12/15, Philip Jägenstedt wrote: > On

Re: [whatwg] VIDEO and pitchAdjustment

On Thu, Mar 3, 2016 at 1:18 AM, Paul Adenot wrote: > That looks appropriate, and is in line with how the Web Audio API does > detuning (using the same unit, [0]). > > That said, I'm not sure about the use case here? Time-stretching (normal > playbackRate) is useful, for example, to watch a confere

Re: [whatwg] VIDEO and pitchAdjustment

That looks appropriate, and is in line with how the Web Audio API does detuning (using the same unit, [0]). That said, I'm not sure about the use case here? Time-stretching (normal playbackRate) is useful, for example, to watch a conference slightly faster in order to save some time. I can't reall

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Mar 2, 2016 at 1:09 PM, Garrett Smith wrote: > On Wed, Mar 2, 2016 at 2:36 AM, Philip Jägenstedt wrote: >> On Wed, Mar 2, 2016 at 5:08 PM, Paul Adenot wrote: >>> >>> Gecko uses code that can do arbitrary pitch adjustment, unrelated to >>> time-stretching (which is speed change with pitc

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Mar 2, 2016 at 2:36 AM, Philip Jägenstedt wrote: > On Wed, Mar 2, 2016 at 5:08 PM, Paul Adenot wrote: >> >> Gecko uses code that can do arbitrary pitch adjustment, unrelated to >> time-stretching (which is speed change with pitch compensation). > > That's neat. If you're interested in ex

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Mar 2, 2016 at 5:08 PM, Paul Adenot wrote: > > Gecko uses code that can do arbitrary pitch adjustment, unrelated to > time-stretching (which is speed change with pitch compensation). That's neat. If you're interested in exposing this as an API on HTMLMediaElement, can you file a spec bug

Re: [whatwg] VIDEO and pitchAdjustment

Gecko uses code that can do arbitrary pitch adjustment, unrelated to time-stretching (which is speed change with pitch compensation). Paul. On Wed, Mar 2, 2016 at 5:00 AM, Philip Jägenstedt wrote: > On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith > wrote: > > On Thu, Nov 12, 2015 at 11:32 AM, Ph

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith wrote: > On Thu, Nov 12, 2015 at 11:32 AM, Philip Jägenstedt wrote: >> On Thu, Nov 12, 2015 at 10:55 AM, Garrett Smith >> wrote: >>> On 11/12/15, Philip Jägenstedt wrote: On Thu, Nov 12, 2015 at 9:07 AM, Garrett Smith wrote: > > O

Re: [whatwg] VIDEO and pitchAdjustment

On Thu, Nov 12, 2015 at 11:32 AM, Philip Jägenstedt wrote: > On Thu, Nov 12, 2015 at 10:55 AM, Garrett Smith > wrote: >> On 11/12/15, Philip Jägenstedt wrote: >>> On Thu, Nov 12, 2015 at 9:07 AM, Garrett Smith >>> wrote: On 10/19/15, Philip Jägenstedt wrote: > On Tue, Sep 1, 201

Re: [whatwg] Support filters in Canvas

Having an opaque handle (CanvasFilter) would be great for Houdini paint. This would mean that when we plumb in a property of CSS type the TypedOM can have an opaque handle to that filter. I.e. registerPaint('x', class { paint(ctx, styleMap) { const filter = styleMap.get('--my-filter').filt

Re: [whatwg] Support filters in Canvas

On Fri, Feb 26, 2016 at 10:40 AM, Anne van Kesteren wrote: > On Fri, Feb 26, 2016 at 4:34 PM, Ali Juma wrote: > > The current canvas filters proposal [1] allows using SVG reference > filters > > defined in external documents (e.g. “url(file.svg#filter)”). Since the > > external document needs to

Re: [whatwg] Support filters in Canvas

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Anne van Kesteren > Perhaps we could support assigning an SVG filter directly (as an object)? > Developers would be responsible to load them if they're external. Adding yet > another network API that's a t

Re: [whatwg] Support filters in Canvas

On Fri, Feb 26, 2016 at 4:34 PM, Ali Juma wrote: > The current canvas filters proposal [1] allows using SVG reference filters > defined in external documents (e.g. “url(file.svg#filter)”). Since the > external document needs to be loaded before the filter can be applied, > there’s a delay between

Re: [whatwg] Support filters in Canvas

]; ctx.strokeText(“SVG”, 50, 200); }); … // Once we no longer need these filters, release them. filters = []; Ali [1] https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Sep/0110.html

Re: [whatwg] Reviving ImageBitmap options: Intend to spec and implement

It's an interesting option to create a non-premultiplied ImageBitmap and convert on to an ImageData. However I was under the impression the point of ImageBitmap was to be drawn "without undue latency", which browsers could interpret as a pre-allocated GPU texture. Doesn't this make it difficult to

Re: [whatwg] Reviving ImageBitmap options: Intend to spec and implement

t; >> potentially-confusing HTML style crossOrigin enums in favor of the > >> RequestCredentials enum used by Fetch: > >> https://fetch.spec.whatwg.org/#requestcredentials. You can see this in > >> e.g. https://github.com/whatwg/html/pull/608 where I chose the same > >&

Re: [whatwg] Reviving ImageBitmap options: Intend to spec and implement

On Thu, Feb 11, 2016 at 9:27 AM, Justin Novosad wrote: > On Wed, Feb 10, 2016 at 2:38 PM, Ashley Gullen wrote: > > > ImageBitmap is not useful for getting the data from: it still requires > > synchronous use of a canvas to turn in to an ImageData. I would encourage > > browser vendors to look at

Re: [whatwg] Reviving ImageBitmap options: Intend to spec and implement

On Wed, Feb 10, 2016 at 2:38 PM, Ashley Gullen wrote: > ImageBitmap is not useful for getting the data from: it still requires > synchronous use of a canvas to turn in to an ImageData. I would encourage > browser vendors to look at my spec proposal to avoid this: > http://wicg.github.io/img-conve

Re: [whatwg] Reviving ImageBitmap options: Intend to spec and implement

redentials enum used by Fetch: >> https://fetch.spec.whatwg.org/#requestcredentials. You can see this in >> e.g. https://github.com/whatwg/html/pull/608 where I chose the same >> initial crossOrigin design and Anne convinced me to move to credentials. I >> imagine we'll

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