{"id":8081,"date":"2021-07-07T20:03:41","date_gmt":"2021-07-07T18:03:41","guid":{"rendered":"http:\/\/plus.maciejpiasecki.info\/index.php\/2021\/07\/07\/google-will-make-re-opening-accidentally-closed-chrome-tabs-instant\/"},"modified":"2021-07-07T22:06:04","modified_gmt":"2021-07-07T20:06:04","slug":"google-will-make-re-opening-accidentally-closed-chrome-tabs-instant","status":"publish","type":"post","link":"https:\/\/plus.maciejpiasecki.info\/index.php\/2021\/07\/07\/google-will-make-re-opening-accidentally-closed-chrome-tabs-instant\/","title":{"rendered":"Google Will Make Re-Opening Accidentally Closed Chrome Tabs Instant"},"content":{"rendered":"<p>Google is now working on a way to make reloading Chrome Tabs that have been accidentally closed on desktop platforms instant. Or as close to instantaneous as is possible. That\u2019s based on the discovery of three new commits in the Chromium Gerrit, found by Android Police.<br \/>\nOf course, Android already has a similar feature, albeit a less efficient one. And Chrome already utilizes a back-forward cache to reload pages instantly, using the back and forward buttons. But the latter is more similar to what Google is working on now. With the change in place, the commits indicate, closed tabs will be left intact in memory. And they\u2019ll stay in memory for 15 seconds, just in case the user didn\u2019t mean to close them.<br \/>\nIf the user restores the tab or tabs within that period, Chrome will reload them as though they\u2019d never been closed at all. Saving users the hassle of waiting if they close a tab by mistake.<br \/>\nWhy does this matter?<br \/>\nNow, Google has already been putting in a lot of work to make closing and reopening tabs easier. In particular, as that applies to accidentally closed tabs and tab groups. And it\u2019s been jumping through hoops to make those features easier to find as well.<br \/>\nThe latest change in that saga is, however, a bit different in that this will be a background change. So users won\u2019t need to do much to take advantage of it and won\u2019t need to learn new browsing habits. As is the case with the abovementioned reading list and bookmarks changes, which will ultimately affect how users access closed tabs.<br \/>\nInstead, as long as users re-open Chrome tabs immediately after closing them, they\u2019ll reload in an instant. Pulled directly from cache with no further interaction from users.<br \/>\nWhen will you see Chrome Tabs with instant reloading?<br \/>\nAs of this writing, the new feature is not quite ready for primetime. It hasn\u2019t even appeared as a Canary flag just yet, in fact. The flag that\u2019s been added for testing purposes internally. So there\u2019s no clear indication as to when end-users will see the improvement.<br \/>\nNew development on features as far out as Chrome 93 has already frozen, as of June 17 and the \u2018feature freeze\u2019 for Chrome 94 is July 29. So Chrome 94 appears to be, for now, the earliest this feature could arrive. Although Google could always add it in earlier if it chooses to. That version of Chrome is slated for desktop platforms in late September \u2014 or early October for Chromebooks.<br \/>\nThe post Google Will Make Re-Opening Accidentally Closed Chrome Tabs Instant appeared first on Android Headlines.&#013;<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/plus.maciejpiasecki.info\/wp-content\/uploads\/2021\/07\/Chrome-Navigation-DG-AH-2021.jpg\" width=\"1600\" height=\"1200\">&#013;<br \/>\nSource: ndroidheadlines.com&#013;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google is now working on a way to make reloading Chrome Tabs that have been accidentally closed on desktop platforms [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":8082,"comment_status":"false","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8081","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bez-kategorii"],"_links":{"self":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/comments?post=8081"}],"version-history":[{"count":1,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8081\/revisions"}],"predecessor-version":[{"id":8083,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8081\/revisions\/8083"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media\/8082"}],"wp:attachment":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media?parent=8081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/categories?post=8081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/tags?post=8081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}