[whatwg] Collecting tips for getting involved in web standards

I'm giving a talk in a couple days at LXJS, and part of it is to teach the attendees how standards work and how they can get involved. I'm putting together tips, based on my experiences over the last year or so, and was wondering if the members of these lists had anything they wanted to

Re: [whatwg] Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments

Eventually ES6 template strings [1] will make this awesome, as you'll do querySelector(css`\n`) or querySelector(css`[data-some-id=${myId}]`) or even qs`[data-some-id=${myId}]` But someone has to write these functions (css and/or qs) and there's no point in creating standard versions until

Re: [whatwg] Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments

From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Ian Hickson I feel this is a case where we're not putting authors first, but are instead putting spec purity first. In terms of not speccing getElementById etc., I see what you mean. But I do want to

Re: [whatwg] Canvas in workers

From: whatwg-boun...@lists.whatwg.org [whatwg-boun...@lists.whatwg.org] on behalf of Anne van Kesteren [ann...@annevk.nl] On Wed, Oct 16, 2013 at 9:23 PM, Kenneth Russell k...@google.com wrote: While the Promise returned from createImageBitmap(HTMLCanvasElement) can be fulfilled immediately,

Re: [whatwg] Add input Switch Type

From: whatwg-boun...@lists.whatwg.org [mailto:whatwg- I agree that the look and feel is different from checkbox but all the differences seem to be purely presentational. If you disagree, you need to elaborate a bit more. Interestingly, Microsoft's Windows Store apps guidelines disagree. I

Re: [whatwg] input type=number for year input

One useful route may be using ECMAScript's Internationalization API to offload any formatting work. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat seems to imply something like input type=number formatstyle=decimal lang=en-US could format

Re: [whatwg] new constructor method for Path2D

What about making the Path2D constructor a property of each context? E.g. var path = new myContext.Path2D(...); Each context would have a different constructor tied to it, allowing this kind of optimization.

Re: [whatwg] Making URLSearchParams set() `value` argument optional

undefined is probably more appropriate than null, but generally this would be nice. We have several URLs in our app at work that are built without = signs; it would be surprising if we couldn't round trip them through the URL parser without losing that. On Mar 12, 2014, at 7:00, Simon Sapin

Re: [whatwg] Promise-vending loaded() ready() methods on various elements

From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Boris Zbarsky // img is already loaded sometimes // Would like to observe a new load var promise1 = img.loaded(); // oops! This will be pre-resolved if // we were

Re: [whatwg] Promise-vending loaded() ready() methods on various elements

There is no such thing as DOM promises. From: Kyle Simpsonmailto:get...@gmail.com Sent: ‎3/‎14/‎2014 20:35 To: whatwg@lists.whatwg.orgmailto:whatwg@lists.whatwg.org Subject: Re: [whatwg] Promise-vending loaded() ready() methods on various elements I'd also like

Re: [whatwg] Proposal: HTMLFormElement#requestAutocomplete() should return a Promise

From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Dan Beam I propose requestAutocomplete()[1] should return a Promise. This has been requested since the creation of this API[2][3] and seems like a natural fit. Web authors can then call

Re: [whatwg] Add a |transient| mechanism to the notifications API

This seems like a valuable feature. I am hopeful something like it can be added. From my reading of Windows Phone 8.1 reviews, the way they handle this is by allowing applications to remove notifications themselves. This seems like the most flexible approach: applications could automatically

Re: [whatwg] Proposal: HTMLFormElement#requestAutocomplete() should return a Promise

From: db...@google.com [mailto:db...@google.com] On Behalf Of Dan Beam So just pass no argument at all (i.e. arguments.length == 0)?  I was under the impression some type of value should always be returned (but I'm biased by blink/v8's current implementation). It's equivalent, both for

Re: [whatwg] hidden attribute useless with display: flex?

On Apr 30, 2014, at 17:44, Tab Atkins Jr. jackalm...@gmail.com wrote: On Wed, Apr 30, 2014 at 2:32 PM, Ian Hickson i...@hixie.ch wrote: On Wed, 30 Apr 2014, Anne van Kesteren wrote: We could change the specification to use display-box instead. That might work. Would that break sites

Re: [whatwg] Fetch API: asHTML

From: annevankeste...@gmail.com annevankeste...@gmail.com on behalf of Anne van Kesteren ann...@annevk.nl However, I could see it instead has to go the other way around. Instead of having a bunch of methods on stream to convert it into various other pieces. Other pieces could have ways of

Re: [whatwg] Fetch API: asHTML

From: Adam Barth w...@adambarth.com It might be instructive to think about how the Node community would structure these APIs. Node has a much stronger notion of modules and dependencies than browsers because Node uses npm. As Node developer, I would be sad if my networking module dragged

Re: [whatwg] Fetch: asFormData()

Hmm. To clarify, this is in case the server sends you application/x-www-form-urlencoded data, and you want to then get it in a format that can easily become a mutable query string or form data object? If so, neither use case seems like they are worth the convenience method to me. Servers

Re: [whatwg] Fetch: asFormData()

From: annevankeste...@gmail.com annevankeste...@gmail.com on behalf of Anne van Kesteren ann...@annevk.nl I expect the common usage scenario to be the page sending such data to a service worker. Note that we have to care about the server side now we have this proxy. That is a great point.

Re: [whatwg] brand-color meta extension

I would like to reiterate that brand- is not a good prefix for this purpose. It has nothing to do with brands, and much more to do with the app or with system integration.

Re: [whatwg] Questions about the Fetch API

From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Juan Ignacio Dopazo jdop...@yahoo-inc.com Would it be to crazy to get fetch(url).asJSON() to work? Either by not having fetch() return a promise (and return something that has a function that returns a promise for the headers) or by

Re: [whatwg] Form Controls Wish List

Hi Garret, I'd really encourage you to read the WHATWG FAQ. In particular, the part urging you to focus on presenting compelling use cases, instead of specific APIs or solutions. Many of your suggestions are not motivated by use cases, from what I can see, and in fact would actively harm

Re: [whatwg] Questions about the Fetch API

From: Juan Ignacio Dopazo jdop...@yahoo-inc.com Why would this not be passing a writable stream object as body parameter? It would have to be a readable stream. Otherwise, how would the request be able to consume it? So most people would have to pass a stream that is both readable and

Re: [whatwg] Questions about the Fetch API

From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Domenic Denicola dome...@domenicdenicola.com Of these, 1 seems much nicer, based on my Node.js experience. To be clearer as to why this is: stream APIs work much better when things you write to are represented as writable streams

Re: [whatwg] Questions about the Fetch API

From: Juan Ignacio Dopazo jdop...@yahoo-inc.com I agree that Node's design sounds a bit better for piping. But where would you put the FetchResponseBodyStream? fetch() returns a promise for a Response. Why would the response have a writable stream for the request? There are two options:

Re: [whatwg] Questions about the Fetch API

Will and I hashed this out offline. Our tentative conclusion for streams is captured in https://github.com/whatwg/streams/issues/146. In short, the issue he brings up is a potential issue for not just the fetch body stream, but for any writable stream. As such it needs to be addressed

Re: [whatwg] Fetch Objects and scripts/stylesheets

I like how fetch is a small primitive right now. We should not overload it with more functionality, but instead create new APIs on top of it. It's important to be able to polyfill those APIs on top of fetch, instead of adding more stuff to the base substrate of fetch itself.

Re: [whatwg] [Fetch] ambiguity problem?

From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Brian Kardell bkard...@gmail.com console. log(o.responseText); console. log(o.responseText); This is why I've been advocating for asJSON() and friends to be verbs, not nouns, i.e. readAsJSON(). Showing how you take an action makes you

Re: [whatwg] Preventing wake lock leaks with DOM nodes

In general I feel this thread has taken a turn for the complex. Why don't we just do what other platforms do, and provide a simple global request/release mechanism (or toggleable Boolean property!), which developers can build on top of? A lot of the ideas here seem to be trying to create the

[whatwg] Object.observe()able properties on the web platform

[Spawning new thread on public-script-coord; whatwg to bcc] From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Jonas Sicking jo...@sicking.cc On Wed, Aug 20, 2014 at 1:33 AM, Anne van Kesteren ann...@annevk.nl wrote: On Wed, Aug 20, 2014 at 10:29 AM, Jonas Sicking jo...@sicking.cc

Re: [whatwg] Canonical Image and Color

From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Mike tomshin...@yandex-team.ru I really believe that the notification api is a related topic but can exist as a separate api used in page icon. I think it’s a good idea not to bind them together. I think there are potentially three

[whatwg] Removing ARIA mappings from the HTML standard in favor of a separate doc

Over in [1] Steve proposes moving the UA requirements for accessibility mapping out of W3C HTML. The corresponding section in WHATWG HTML is [2]. Recently I tried to do implementer-ey things [3] but found the delineation between authoring and UA requirements in that section very confusing. So I

Re: [whatwg] Removing ARIA mappings from the HTML standard in favor of a separate doc

From: Ian Hickson [mailto:i...@hixie.ch] I think the author and UA requirements are tightly related, however (e.g. the ARIA spec term strong semantics implies both), so I don't think it makes sense to move one and not the other. The problem is, there are multiple sources of truth for the

[whatwg] An API for unhandled promise rejections

## Problem A common desire in web programming is to log any uncaught exceptions back to the server. The typical method for doing this is window.onerror = (message, url, line, column, error) = { // log `error` back to the server }; When programming asynchronously with promises,

Re: [whatwg] An API for unhandled promise rejections

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Boris Zbarsky As usual, if one or both of these events is missing listeners, nothing will happen. I'm not sure that's usual. I think I misspoke here. The events will still be fired! Anything else would be insanity. I just

Re: [whatwg] An API for unhandled promise rejections

From: Boris Zbarsky [mailto:bzbar...@mit.edu] On 9/12/14, 3:19 PM, Domenic Denicola wrote: If there is no listener for either when the promise would normally fire error, but then a listener for rejectionhandled gets added before a .catch() call on the promise, does the listener get called

Re: [whatwg] An API for unhandled promise rejections

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Boris Zbarsky In this case the event would be fired By the event do you mean the error event or the rejectionhandled event? Ah, trick question! Because, see, I was confused when I wrote that, and myself did not know! but no

Re: [whatwg] Notifications: making requestPermission() return a promise

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Tab Atkins Jr. This is actually kinda terrible. Promises make it *really easy* to deal with rejections *later*, letting you execute a bunch of code on the success path and only at the end saying Oh, did something along the

Re: [whatwg] Notifications: making requestPermission() return a promise

On Oct 1, 2014, at 16:59, Tab Atkins Jr. jackalm...@gmail.com wrote: On Wed, Oct 1, 2014 at 11:44 AM, Domenic Denicola dome...@domenicdenicola.com wrote: From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Tab Atkins Jr. This is actually kinda terrible. Promises make

Re: [whatwg] Notifications: making requestPermission() return a promise

On Oct 1, 2014, at 18:22, Tab Atkins Jr. jackalm...@gmail.com wrote: On Wed, Oct 1, 2014 at 1:02 PM, Tobie Langel tobie.lan...@gmail.com wrote: On Wed, Oct 1, 2014 at 5:59 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: I've never heard this opinion explicitly expressed, and it has never

Re: [whatwg] Notifications: making requestPermission() return a promise

My previous replies to this thread have been about more general issues regarding promises and exceptions where I felt the need to jump in. Now, about the actual specific case at hand... From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Anne van Kesteren Otherwise I would

Re: [whatwg] Notifications and service workers

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Jonas Sicking Generally speaking we tend to leave UI up to browsers and avoid speccing it. However given that notifications is all about UI I think doing so effectively makes the feature untrustable for authors. We don't need

Re: [whatwg] Notifications: making requestPermission() return a promise

From: Tab Atkins Jr. [mailto:jackalm...@gmail.com] Again, if this means that the current design for await becomes less convenient, *we can fix await to work better*. It's not set in stone, it's not developed yet. This is a thing we can change. To be clear, this will not be happening.

Re: [whatwg] Notifications: making requestPermission() return a promise

From: annevankeste...@gmail.com [mailto:annevankeste...@gmail.com] On Behalf Of Anne van Kesteren I don't think you should need try/catch for a common failure case. Ah, this is the crux of our minor-disagreement, I think. IMO using try/catch for a common failure case is fine, *as long as you

Re: [whatwg] Controlling the User-Agent header from script

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Roger Hågensen Also, a script being able to set a custom XMLHttpRequest User-Agent would be nice. Not necessarily replace the whole thing but maybe concatenate to the end of the browser one? That way a webmaster would be

Re: [whatwg] Proposal: Write-only submittable form-associated controls.

For the XSS attacker, couldn't they just use `theInput.removeAttribute(writeonly); alert(theInput.value);`? Or is this some kind of new un-removable attribute?

Re: [whatwg] allow link in body + DOM position as a rendering hint

For import at least I think this change is important (insofar as any authoring conformance criteria is important). See e.g. https://github.com/bterlson/ecmascript/blob/master/spec/index.html for a usage of link rel=import as a kind of include HTML here macro that I find to be a useful pattern.

Re: [whatwg] HTML video and IE, Safari, Firefox, Chrome

Impressive research, Martin! Would you and your team be willing to turn it into test cases for the web-platform-tests project [1]? That's usually a good way to get browsers to fix their bugs. Failing that, you might want to file bugs on the various browser bug trackers. [1]:

Re: [whatwg] [url] Feedback from TPAC

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of David Singer (I don't have IE to hand at the moment). I tried to test IE but unfortunately it looks like the URL components from DOM properties part of the demo page does not work in IE, I think because IE doesn't support

[whatwg] Feedback wanted on integrating fetch request/response and streams

In https://github.com/yutakahirano/fetch-with-streams Yutaka, Anne, and I are working on how to integrate the fetch API with streams. The general pattern we want is that for both request and response objects their creator is given a writable stream to write body content to, using [the revealing

Re: [whatwg] Wish for HTMLFormElement.checkValidity(boolean)

You may be interested in form.reportValidity().

Re: [whatwg] URL interop status and reference implementation demos

Really exciting stuff :D. I love specs that have reference implementations and strong test suites and am hopeful that as URL gets fixes and updates that these stay in sync. E.g. normal software development practices of not changing anything without a test, and so on. From: whatwg

Re: [whatwg] URL interop status and reference implementation demos

From: Sam Ruby [mailto:ru...@intertwingly.net] Done, sort-of: https://url.spec.whatwg.org/interop/browser-results/ Excellent, this is a great subset to have. I am curious what it means when testdata is in the user agents with differences column. Isn't testdata the base against which the user

Re: [whatwg] URL interop status and reference implementation demos

From: Sam Ruby [mailto:ru...@intertwingly.net] These results compare user agents against each other. The testdata is provided for reference. Then why is testdata listed as a user agent? I am not of the opinion that the testdata should be treated as anything other than as a proposal at

Re: [whatwg] URL interop status and reference implementation demos

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of James Graham That sounds like unnecessary complexity to me. It means that random third party contributers need to know which repository to submit changes to if they edit the urld testata file. It also means that we have to

Re: [whatwg] URL interop status and reference implementation demos

From: Sam Ruby [mailto:ru...@intertwingly.net] I guess I didn't make the point clearly before. This is not a waterfall process where somebody writes down a spec and expects implementations to eventually catch up. That line of thinking sometimes leads to browsers closing issues as

Re: [whatwg] Need clarification on activation behavior for menuitem of type=checkbox

The causality you are assuming seems backward here. Activation behavior is triggered by clicks, so the sequence is roughly User clicks (or .click is called) - { activation behavior happens, click event triggered } See https://html.spec.whatwg.org/multipage/interaction.html#activation for the

Re: [whatwg] alternate ids for elements

I too have run into this (specifically wanting to preserve old deep-links) and think it would be reasonable, in theory. However, in practice I see no reason for browsers to expend valuable engineering resources on this when an empty `div` (or, more traditionally, an empty `a id=/a`) suffices

Re: [whatwg] why FormData dosen't support x-www-form-urlencoded ?

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of block.rxckin.be...@gmail.com What is the motivation to not support except multipart format in FormData ? Anne already answered you, but I'll re-state his answer as a question: What do you expect the browser to do if your form

Re: [whatwg] why FormData dosen't support x-www-form-urlencoded ?

From: Garrett Smith [mailto:dhtmlkitc...@gmail.com] I would expect the filename to be sent as the value. Blobs don't have filenames.

Re: [whatwg] An API for unhandled promise rejections

://github.com/iojs/io.js/pull/758 [2]: https://gist.github.com/benjamingr/0237932cee84712951a2 [3]: https://gist.github.com/domenic/9b40029f59f29b822f3b#promise-error-handling-hooks-rough-spec-algorithm -Original Message- From: Domenic Denicola Sent: Friday, September 12, 2014 14:34 To: WHATWG

Re: [whatwg] HTTP/2 push detection and control in JavaScript

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Brendan Long It’s not clear to me how we would cancel a pushed stream, or retrieve streaming body data without waiting for the request to completely finish. Working on that: - http://streams.spec.whatwg.org/ -

Re: [whatwg] An API for unhandled promise rejections

Ping. We're considering implementing this in Chrome and it would be helpful to get a sense if other vendors support this. -Original Message- From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Domenic Denicola Sent: Monday, February 9, 2015 20:45 To: WHATWG Cc: Petka

Re: [whatwg] An API for unhandled promise rejections

The OP proposal. -Original Message- From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Elliott Sprehn Sent: Monday, May 18, 2015 19:23 To: Domenic Denicola Cc: WHATWG; Boris Zbarsky; Brian Terlson Subject: Re: [whatwg] An API for unhandled promise rejections What

Re: [whatwg] Fetch, MSE, and MIX

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Anne van Kesteren Well, except now you make yourself depend on some definition of an opaque stream object which nobody has defined yet. Perhaps we should, but that will take longer and won't be less work (though maybe less

Re: [whatwg] An API for unhandled promise rejections

From: Boris Zbarsky [mailto:bzbar...@mit.edu] We (Mozilla) support having something here. Great! Thanks for your reply. And sorry for the lack of the specifics. We'll work on nailing something down (spec-wise) as we implement, and of course far ahead of any shipping. I'll reply when I get a

Re: [whatwg] An API for unhandled promise rejections

From: Jonas Sicking [mailto:jo...@sicking.cc] An API being proposed on a mailing list such as this one? The API is already proposed (see the rest of this thread). The exact timing is tricky to figure out without a working implementation to play with, compare to real-world code, tweak, adjust,

Re: [whatwg] An API for unhandled promise rejections

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Jonas Sicking That sounds hard to provide feedback on... What working mode would you prefer?

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

I'm pretty sure it's out of scope. That's really asking to specify how OS-level task switching works. I imagine that Safari-wrapper or whatever has decided that 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

Re: [whatwg] An API for unhandled promise rejections

, June 17, 2015 14:40 To: wha...@whatwg.org; Domenic Denicola Subject: Re: [whatwg] An API for unhandled promise rejections Hi Domenic, Sorry to re-open an old thread; but this is important to me :). Do you know if there’s been any progress on getting this behavior standardized (or even

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] 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] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Rick Byers That seems like a nice incremental compromise. Using a new name for addEventListener will help address some of the feature detection / compatiblity concerns too. Filed

Re: [whatwg] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

From: Anne van Kesteren [mailto:ann...@annevk.nl] 2) Should mayCancel=false listeners always get an Event with cancelable=false, or is this just a hint such that all listeners still get the same event with the same properties. https://github.com/RByers/EventListenerOptions/issues/2 I was

Re: [whatwg] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

Generally nobody wants to write code in their JavaScript engine implementation that is aware of concepts like the DOM, events, methods specifically named preventDefault, etc. -Original Message- From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Ashley Gullen Sent:

Re: [whatwg] VIDEO and pitchAdjustment

To be clear: Everyone can imagine use cases for playing videos backward. However, so far the only statements we have about implementations are negative. My subthread was more concerned with making the spec reflect current reality. If you can convince implementers to support backward videos,

Re: [whatwg] VIDEO and pitchAdjustment

From: Eric Carlson [mailto:eric.carl...@apple.com] > FWIW, Safari supports negative playback rates on the desktop and on iOS. > > ... > > The crash Garrett noted in Safari 8 is a bug that “only" happens with MSE > content. That's really helpful, thanks. Combined with Edge's keyframes-only

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 to have the

Re: [whatwg] VIDEO and pitchAdjustment

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Robert O'Callahan According to the spec it should work, but it's very low priority for us and implementing it would be very inefficient as Yay295 describes. So I don't think it's going to happen in Firefox in the forseeable

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 compat

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's good

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 much in

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

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Xida Chen > We intend to push this feature forward in Blink, particularly we intend to > spec and implement the "Strongly desired options" listed on the Whatwg > proposal page. We would appreciate comments and suggestions on the >

Re: [whatwg] Opinions on window.console = "foo", and other oddities of window.console

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Boris Zbarsky > What was the outcome of the discussions about possibly having "interface > console" and having all the methods be statics? Another good question which we should probably resolve ASAP. It does indeed change the

Re: [whatwg] Opinions on window.console = "foo", and other oddities of window.console

From: Domenic Denicola > So I think the plan of record is: `attribute any console`, with prose > describing > how the getter returns "the window's console object" which is initially set to > a new instance of Console, but the setter can change it to any value. This > m

[whatwg] Opinions on window.console = "foo", and other oddities of window.console

As you may know, we now have a standard for the console object: http://console.spec.whatwg.org/ One of the first issues we encountered while investigating console behavior is https://github.com/whatwg/console/issues/1, which is that browsers currently allow setting `window.console` (and

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 thin layer on top of

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:

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 operating

Re: [whatwg] Galleries revisited

> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of > i...@hansschmucker.de > The remaining issue for me seems that the interaction between this "viewer" > and the page is completely unspecified and that items like descriptions and > copyright notices which may be required to

Re: [whatwg] VIDEO and pitchAdjustment

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Garrett Smith > What is the status on this? I believe the conclusion of the thread was that this is possible with the Web Audio API.

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 like to discuss

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 canvas element.

Re: [whatwg] Backend Implementation

From: Jacob Villarreal [mailto:jv1...@yahoo.com] > I'm trying to get some information on how to implement some new > tags/attributes on the backend.  I would like to know if my only option is > the use case discussion, or if there are other resources for getting it done. Yes, we aren't

Re: [whatwg] Proposal for a new standard for HTML

Hi Jacob, and welcome to the WHATWG. Have you read https://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F ? In particular, it seems you've jumped straight to step 7. Can you instead start with steps 1 and 2, and describe the problems you are trying to

Re: [whatwg] Proposal Update

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Jacob Villarreal > I finally got my proposal straightened out.  It's as simple as follows: Hi Jacob, I would respectfully ask that you stop using this list for your proposal. So far you have created four separate threads and

Re: [whatwg] What's the element for a paragraph label?

Hi Brenton, great to have you here. From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of brenton strine > Is there a semantic element that can be used in a situation like this? If so, > I > propose adding "label" to the specification for that element. > > Then again, maybe this

Re: [whatwg] window.opener security issues (Was: WhatWG is broken)

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Ian Hickson > I believe that's a bit of an overstatement. There are certainly risks > involved in window.opener (they're briefly discussed in the spec itself), but > it doesn't remove the origin checks. This is the crucial

Re: [whatwg] window.opener security issues (Was: WhatWG is broken)

From: Zac Spitzer [mailto:zac.spit...@gmail.com] > how about rather than requiring this on every why not support a base tag > directive  for the whole document i.e. , similar to > ? Yes, this is a good idea to include in a general framework for imposing such

Re: [whatwg] Arithmetic coded JPEGs

Hi Evgeny, and welcome to the list! From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Evgeny Vrublevsky > Unfortunately, browsers still don't support arithmetic JPEG officially. Is > this a right place to start a discussion if it is possible to change it? This is a reasonable

Re: [whatwg] Moving PNG Extensions to WhatWG

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Christoph Päper > lists APNG as a possible > specification to take under WhatWG wings. It currently lives dormant at > . What would be

  1   2   >