5 ms·

Spoiler: is a Chrome-only feature

• mywittyname 7y ago
  Presumably the results translate well enough to other browsers, barring some idiosyncrasies with certain features (e.g, canvas has a memory leak in certain situations in Safari).
• neuronexmachina 7y ago
  It's also currently only in the dev version: > The performance.measureMemory() API is available as an origin trial in Chrome 83. The origin trial is expected to end in Chrome 84. Chrome 83 will be released as stable on May 19: https://www.chromestatus.com/features/schedule https://www.chromestatus.com/features/schedule
• kaycebasques 7y ago
  I work on web.dev and would like your feedback on how we're handling cross-browser compatibility information. I'm aware that it's the biggest frustration for web developers based on the MDN DNA report [1] (overall needs ranking on page 19, items 1, 3, 4, 5). * Is there an ideal location for cross-browser information? E.g. top of page, bottom of page, middle of page. * Are we communicating the information effectively? E.g. is there anything important that we're missing. * (On a more general note) Is there specific guidance related to cross-browser compatibility that you think would be helpful for us to write about? The more specific, the better. [1] https://mdn-web-dna.s3-us-west-2.amazonaws.com/MDN-Web-DNA-Report-2019.pdf https://mdn-web-dna.s3-us-west-2.amazonaws.com/MDN-Web-DNA-R...
  • lol768 7y ago
    > * Is there an ideal location for cross-browser information? E.g. top of page, bottom of page, middle of page. Ideally, it'd be right at the top of the article so I understand immediately that this isn't production-ready yet and I can read the rest of the article in that light (as something I can experiment with potentially, via the origin trial).
  • alberth 7y ago
    Thanks for all your work on web.dev Question: can this functionality be exposed in Lighthouse/PageSpeed audit results?