Live data from Hacker News

Viewing profile — mathias

mathias

HN member
Joined
Sat, Dec 26, 2009, 1:44 PM UTC
HN karma
3,588
Public activity
285 items

About mathias

Web standards enthusiast. https://mathiasbynens.be/

Recent public activity

  1. comment
    Comment #34903679

    Did you know that “old” Chrome Headless (2017–2023) was a separate, alternate browser implementation that just happened to be shipped as part of the same Chrome binary? It doesn’t …

  2. story
  3. comment
    Comment #24212921

    https://github.com/puppeteer/recorder

  4. story
  5. comment
    Comment #19902070

    The article includes a working polyfill that includes old IE support.

  6. comment
    Comment #19902060

    Author of the referenced article here. The article includes a working polyfill that includes old IE support, so I’m not sure what you’re complaining about. Also, saying “jsvu is th…

  7. story
  8. comment
    Comment #19736804

    Thanks :) Glad to see people appreciate simplicity (and the performance that comes with it).

  9. comment
    Comment #18706479

    We do indeed measure improvements against more than one website. We wouldn’t want to improve website X while regressing the rest of the internet. See https://v8.dev/blog/real-world…

  10. comment
    Comment #18674492

    The article links to the explanation by the proposal champions: https://github.com/tc39/proposal-class-fields/blob/master/PR...

  11. comment
    Comment #18558449

    I mean, they have been solved. With the exception of String#matchAll (which is currently a Stage 3 proposal), all these features are part of ES2018 and shipping in Chrome. Other br…

  12. comment
    Comment #18558433

    I make sure to keep the article up-to-date. It correctly states the status for each of the features. They’re all part of ES2018 with the exception of String#matchAll which is curre…

  13. comment
    Comment #18558431

    Hey, I’m the author of the article. Despite its age, it’s still accurate and up-to-date. > these features aren't entirely new Depends on what you mean by that. These features are s…

  14. comment
    Comment #18283350

    That’s not very JavaScript-y. Where else in ECMAScript are constants used like this?

  15. comment
    Comment #17966084

    That would be a Chromium feature. V8 only implements ECMAScript and WebAssembly.

  16. story
  17. story
  18. story
  19. comment
    Comment #16232961

    The article is two years old but still up-to-date. The links to the relevant browser bugs are in the document, and the Edge bug is still unresolved. https://wpdev.uservoice.com/for…

  20. comment
    Comment #15638169

    > In older browsers, useCapture is NOT an optional parameter Which browsers are those?

  21. comment
    Comment #15636917

    > Which means you can’t practically use the new form without feature detection. That does not follow. `{ capture: true }` works in both, since it’s an object, and thus truthy. Ther…

  22. comment
    Comment #15536860

    That’s not equivalent though — in the article’s example, imagine `element` is `undefined`, for example. `then()` wouldn’t be called in that case.

  23. comment
    Comment #15536845

    Correct. By Stage 3, the proposal is supposed to be stable enough to start shipping it in stable browsers.

  24. story
  25. comment
    Comment #14124755

    Wondering what a given legacy HTML color value (as seen in `bgcolor`, `text`, `link`, `vlink`, and `alink` attribute values) looks like? This tool (which I made for a presentation …