4 ms·
This article is about Chrome's implementation of the W3C Page Lifecycle API[1]. In the long-term, this approach applies across all browsers, contrary to the cur
by saidajigumi 8y ago
This article is about Chrome's implementation of the W3C Page Lifecycle API[1]. In the long-term, this approach applies across all browsers, contrary to the current HN title's implication that this is a Chrome-specific solution.
[1] https://wicg.github.io/page-lifecycle/spec.html https://wicg.github.io/page-lifecycle/spec.html
- sctb 8y agoWe've just updated the title from ‘Chrome’s solution to the “too many tabs” memory problem’. There are many reasons not to editorialize titles when submitting, and the likelihood of saying something misleading is one of them. > Otherwise please use the original title, unless it is misleading or linkbait. Don't editorialize. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- scrollaway 8y agoI don't think it's a bad edit. It would be better to have both, but "Page Lifecycle API" doesn't actually tell you what that API is for --- it doesn't even tell you it's a web browser API. I think a better title would be: "Page Lifecycle API - A solution to the 'Too Many Tabs' memory problem".
- Fnoord 8y agoNo. "Page Lifecycle API" from "developers.google.com" gives a hint that the article is written by Google and given "developers" is about an open source (or open API at least) Google product, and presto in the first paragraph: "[...] shipping in Chrome 68 [...]". The title is perfectly fine as it is.