| 09:20 | <haywirez> | hey, i'm new and pretty clueless so sorry for potential annoyances i might be causing... i have two main concerns at the moment, both related to the <audio>/media elements. |
| 09:20 | <haywirez> | 1) preservesPitch - this does not seem to be in the spec, but is essential to proper creative uses and what i'm trying to make (a dj-able web player with decent scrubbing/pitching - ccan be easily accomplished by setting this flag to false). are there any reasons why this is so? i see that it's not properly implemented in Chrome even under -webkit prefix for now, but what are the downsides? |
| 09:20 | <haywirez> | 2) playbackRate - in practice it seems to be constrained to values between 0.5 - 4. this is also undesirable, why can't they be negative and the range much wider? both seem like arbitrary constraints that are unnecessarily restrictive |
| 09:23 | <haywirez> | the spec says that the value should be double |
| 09:25 | <jochen__> | annevk: wondering whether i'm reading the URL spec correctly (or specifically, assigning to location.href) |
| 09:26 | <jochen__> | annevk: is my understanding correct that we'd strip leading unicode control characters, resulting in a validation error, but not a failure, and therefore continue with setting the location if the rest of the string is a correct url? |
| 09:26 | <deanedridge> | I think annevk is still on vacation, jochen__ |
| 09:26 | <jochen__> | ah :/ |
| 09:26 | <jochen__> | any other URL experts ? :) |
| 09:27 | <deanedridge> | Many of the WHATWG people are in the US and it's still the weekend there. |
| 10:26 | <kochi> | smaug____: a few tests in http://w3c-test.org/shadow-dom/untriaged/html-elements-in-shadow-trees/html-forms/ |
| 10:30 | <kochi> | historically, most of tests under "shadow-dom/untriaged" were originally contributed from contracted vendor in v0 era. They were converted to v1 where possible, but the coverage and the quality of the tests are quite questionable :( |
| 10:31 | <kochi> | Maybe we can throw them away completely. |
| 14:31 | <mnkk> | hi! i am a coding noob trying to query an API and therefore stumbled upon fetch API |
| 14:31 | <mnkk> | what I still dont get is how do i actually use fetch API to query an API? |
| 14:32 | <mnkk> | to i create a document? |
| 14:32 | <mnkk> | do i use command line? |
| 15:11 | <Domenic> | haywirez: preservesPitch: nobody has come up with an interoperable spec for how it works, and gotten in unprefixed. We should probably do so though, given it's implemented in a couple places. Not sure on the latest status. |
| 15:12 | <Domenic> | haywirez: playbackRate: in practice browsers haven't devoted the engineering resources to giving us infinitely customizable playback rates. The spec doesn't mandate that they support any playback rate in the double range; in fact UAs are supposed to throw if a range is not supported. |
| 15:13 | <Domenic> | jochen__: that looks correct from the current spec. You can generally test against the unofficial reference implementation at https://jsdom.github.io/whatwg-url/ |
| 16:20 | <haywirez> | Domenic: thanks for the updates! |
| 21:16 | <thardin> | woop |
| 22:49 | <smaug____> | dtapuska: why MessageEvent would need .userActivation? |
| 22:52 | <smaug____> | filed an issue |