Re: Improvements to Web IDL exception message strings

On Friday, February 7, 2020 at 8:55:45 AM UTC-5, Boris Zbarsky wrote: > Hello all, > > We just made some changes to how exception strings from ErrorResult get > formatted [1]. The changes apply to both the Throw* DOMException > methods and ThrowTypeError/ThrowRangeError. > > In the new setup,

Re: Intent to implement and ship: built-in CSS counter 'list-item'

(On-list this time) > However, the actual semantics for how list items work are exclusively defined > by CSS ([css-lists], [css-pseudo]). > The above mentioned HTML elements/attributes simply maps to the relevant CSS > properties, using a built-in 'list-item' counter. Where does [css-lists]

Re: Intent to implement and ship: built-in CSS counter 'list-item'

It's great to hear that this isn't a regression in the way I expected. I think I was thrown off by the phrasing of the OP, which implied to me a switch from following the HTML spec to following the CSS lists spec. As I noted, the CSS lists spec contradicts the HTML spec, e.g. disallowing

Re: Intent to implement and ship: built-in CSS counter 'list-item'

On Sunday, March 24, 2019 at 10:21:10 PM UTC-7, Domenic Denicola wrote: > the tests at > https://github.com/web-platform-tests/wpt/tree/master/html/semantics/grouping-content/the-ol-element correction, https://github.com/web-platform-tests/wpt/tree/master/html/semantics/grouping-c

Re: Intent to implement and ship: built-in CSS counter 'list-item'

Some time ago we spent some effort documenting a cross-browser mostly-interoperable behavior for list-item-like behaviors, in https://github.com/whatwg/html/pull/2002 and linked threads. The result is the spec at https://html.spec.whatwg.org/multipage/grouping-content.html#list-owner and the

Re: Intent to explore: A declarative low level graphics API that has a simple mapping to CSS

Hi Victor, I'd love to read about this, but am not a Mozillan. Is there a reason the document is being kept private? ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

RE: Intent to ship: SourceMap header

From: mozilla.dev.platf...@googlegroups.com [mailto:mozilla.dev.platf...@googlegroups.com] On Behalf Of L. David Baron > > On Friday 2017-05-26 11:53 -0600, Tom Tromey wrote: >> How would I go about starting this? >> I have never done anything with web standards before. > > Probably something

Re: Intent to ship: SourceMap header

(Re-sending as I was informed that "posting by email is not allowed"; apologies to those who get this email twice.) From: mozilla.dev.platf...@googlegroups.com [mailto:mozilla.dev.platf...@googlegroups.com] On Behalf Of L. David Baron > > On Friday 2017-05-26 11:53 -0600, Tom Tromey wrote: >>

Re: Avoiding jank in async functions/promises?

On Thursday, May 18, 2017 at 4:34:37 AM UTC-4, smaug wrote: > FWIW, I just yesterday suggested in #whatwg that the platform should have > something like IdlePromise or AsyncPromise. > And there is the related spec bug > https://github.com/whatwg/html/issues/512#issuecomment-171498578 In my

Re: Intent to ship: SharedArrayBuffer and Atomics

Great writeup Lars! It's been a pleasure working with you on this. I just wanted to note that we've finalized the set of Web GL APIs which accept shared memory, and that's been deployed into the latest spec, via the pull request https://github.com/KhronosGroup/WebGL/pull/2387. You can see the

Re: Removing navigator.buildID?

On Monday, October 31, 2016 at 10:54:11 AM UTC-4, Mike Taylor wrote: > On 10/31/16 9:16 AM, Henri Sivonen wrote: > > On Oct 31, 2016 16:02, "Mike Taylor" > > wrote: > >> > >> > >> > >> On 10/29/16 9:21 AM, Kohei Yoshino wrote: > >>> > >>> I think now

Re: Intent to implement and ship: DOMTokenList.prototype.supports

On Tuesday, May 3, 2016 at 4:24:26 PM UTC-4, Boris Zbarsky wrote: > In practice, this is the set of values I'm claiming we > support: "import" (if IsImportEnabled()), "prefetch", "dns-prefetch", > "stylesheet", "next", "alternate", "preconnect", "icon". Anything else > I'm missing? Do we do

Re: Intent to implement and ship: rel="noopener" on links

On Monday, April 25, 2016 at 2:09:07 PM UTC-4, Boris Zbarsky wrote: > 1) This is not feature-detectible, as far as I can see. So it's not > clear to me that sites will know they can use this, short of relying on > browser sniffing. If you implement DOMTokenList.prototype.supports, it should

Re: Intent to ship: navigator.hardwareConcurrency

On Tuesday, March 15, 2016 at 2:08:50 AM UTC-4, Boris Zbarsky wrote: > On 3/15/16 12:59 AM, Domenic Denicola wrote: > > Filed https://github.com/whatwg/html/issues/879; should be able to have it > > in the spec by sometime tomorrow. > > Thank you. That's a lot more us

Re: Intent to ship: navigator.hardwareConcurrency

On Tuesday, March 15, 2016 at 12:26:21 AM UTC-4, Boris Zbarsky wrote: > * Link to standard: You're funny. People don't bother to put stuff into > actual specs anymore. The closest we have is > https://wiki.whatwg.org/wiki/NavigatorCores which does at least have > some IDL and some discussion

Re: Please do not use the Date type in Web IDL APIs

On Friday, October 16, 2015 at 3:12:05 PM UTC-4, Jonas Sicking wrote: > On Fri, Oct 16, 2015 at 11:44 AM, Boris Zbarsky wrote: > > So if you want to have value type like behavior, use a value type; for now > > long long (in IDL terms; Number in JS terms) is good > > FWIW, when