@tomayac do you know why page lifecycle repo has been deprecated? No suggestion, hint or advise.
=> More informations about this toot | More toots from userquin@webtoo.ls
@userquin I don't know why development stopped (the repo https://github.com/wicg/page-lifecycle/ is just dormant, not archived), and failed to find out doing research. Maybe @philipwalton knows? It seems like it failed to get traction with other vendors; I only found this reference https://discourse.mozilla.org/t/page-lifecycle-api-implementation-including-freeze-and-resume-hooks/30465.
=> More informations about this toot | More toots from tomayac@toot.cafe
@tomayac @userquin were you referring to this repo being archived? https://github.com/googleChromeLabs/page-lifecycle
=> More informations about this toot | More toots from philipwalton@toot.cafe
@philipwalton @tomayac yes
=> More informations about this toot | More toots from userquin@webtoo.ls
@userquin @tomayac the repo was automatically archived because there hadn't been recent contributions and we didn't have plans to add features to it.
The library itself should still work just fine, and we could always unarchive it if spec work continues on the API itself, but at this point I'm not aware of any plans to spec new Page Lifecycle API features beyond what was added in 2018.
=> More informations about this toot | More toots from philipwalton@toot.cafe This content has been proxied by September (ba2dc).Proxy Information
text/gemini