New
- Pinned tabs show in every window of the profile. A new window used to open without the pins the first one had. Every window of a profile now shows its pinned tabs and groups, and pinning, unpinning, reordering or renaming one carries to the others. A pin loads its page the first time you click it in a window, so it is never taken from another. Private windows and Little Ardia show none.
- Resize Picture in Picture with ⌘ + scroll or a pinch. Hold ⌘ and scroll over the floating video, with a wheel or a trackpad, or pinch on a trackpad, to make it bigger or smaller. It keeps its shape, stays on screen and sticks to the screen edge it sits near. The next Picture in Picture opens at the size you left it. Plain scrolling is unchanged.
- Hiding the sidebar slides. ⌘S and the toolbar’s sidebar button now slide the sidebar away and back on Dia’s spring, with the page following along. Before, a big session froze the window for one to two seconds. The sidebar button is always there now, even in a narrow sidebar, where it used to be dropped.
- With the address bar in the sidebar, hiding it works like Arc. The page takes the whole window, with no toolbar left behind. Move to the window’s left edge and the sidebar floats in over the page, address bar and all. Its sidebar button docks it again.
Faster
Ardia 0.2.17 against this release, measured on the same Mac. The biggest win: with one tab open and nothing happening, it now uses a sixth of the CPU and wakes the Mac a seventh as often.
| 0.2.17 | 0.2.28 | Change | |
|---|---|---|---|
| Opening the app | 632 ms | 572 ms | −10% (faster) |
| Opening the app, until the first page has painted | 693 ms | 634 ms | −8% (faster) |
| Opening the app for the first time after an update | 6043 ms | 4333 ms | −28% (faster) |
| Switching tabs | 51 ms | 32 ms | 1.6× faster (−37%) |
| Opening a new tab, until its page has painted | 156 ms | 121 ms | −22% (faster) |
| Opening a new window | 83 ms | 83 ms | same |
| ⌘T until you can type in the command bar | – | 60 ms | – |
| A keystroke in the command bar until its suggestions show | – | 18 ms | – |
| A keystroke in the command bar: the app’s own work | – | 3 ms | – |
| Typing 30 keys in the command bar: screen updates | – | 127 | – |
| Typing 30 keys in the command bar: views redrawn | – | 1427 | – |
| Doing nothing with 1 tab open: CPU | 1.20% | 0.19% | 6.3× less (−84%) |
| Doing nothing with 1 tab open: wake-ups per second | 47.1 /s | 7.0 /s | 6.8× fewer (−85%) |
| Doing nothing with 20 tabs open: CPU | 1.99% | 1.15% | 1.7× less (−42%) |
| Doing nothing with 20 tabs open: wake-ups per second | 65.0 /s | 29.5 /s | 2.2× fewer (−55%) |
| Memory with 1 tab open | 328 MB | 288 MB | −12% (less) |
| Memory with 20 tabs open | 1257 MB | 1195 MB | same |
- A launch with several windows shows the front one first. The window you were using no longer waits for the others to be built, which is about a second sooner. The rest appear behind it, in the same order and places as before.
- The page you left open starts loading at launch. Ardia begins the front window’s page before the window itself is up, so it is further along when you see it.
- A page typed into a new tab paints sooner. The New Tab page keeps a hidden tab ready, so Enter only has to load the page: about half the time it took in 0.2.27.
- Switching tabs stays quick with many tabs open. A switch no longer rebuilds the list of pages for every tab, and a tab you can’t see stops reacting to changes.
- Command-bar suggestions come up faster. Each keystroke does a fraction of the matching work it did.
- The first launch after an update is faster. The app is smaller, and the update is checked by macOS ahead of time, so the first start doesn’t wait on those checks.
Fixed
- Links from other apps open in the profile you used last. A link from Mail or Slack always went to the default profile, so on a second profile it opened Little Ardia in the wrong one. It now follows the window you used last, as in Chrome. A private window counts as the profile it was opened from, so Little Ardia is never private and never shares its cookies.
- Private windows have their own private session per profile. Every private window used Personal’s private session, even one opened from another profile. Now a private window belongs to the profile it was opened from, shares its session with that profile’s other private windows, and ends it with the last one.
- Clear Site Data and site settings in a private window leave the regular profile alone. Clearing a site’s data in a private window wiped the regular profile’s cookies for that site, and a permission you set there was kept in the regular profile for good. Both now stay in the private session. The cookie and autofill import commands refuse to run in one.
- Private downloads no longer show up in regular windows. They were listed there, and saved to the downloads list for next time. They now appear only in that session’s private windows and are gone when the last one closes.
- A window lists only its own profile’s downloads. Every regular window listed the downloads of every profile.
- A tab an extension opens lands in its own profile. When the window it opened from no longer showed that profile, the tab could appear in another profile, signed in with the wrong cookies. It now opens in a window of its own profile.