4 ms·

“Should” is doing a lot of work in this sentence. It very much should not do this, if it’s following normal AppKit conventions. Might be a nice optional featu

“Should” is doing a lot of work in this sentence. It very much should not do this, if it’s following normal AppKit conventions. Might be a nice optional feature request…

sitzkrieg 3y ago
where is pinned vs normal tab treatment for closing in appkit conventions?
- c-hendricks 3y ago
  This seems pedantic. Pinned Tabs can be considered like an entry in your bookmark bar. Yes, they're in a different place, but they're a button in the UI, in all windows of the browser, that takes the user to a URL. What's going on here is the user is closing the last tab in their window and expecting it to stay open.
  - sitzkrieg 3y ago
    so to put it more simply, a pinned tab behaves like a button so it doesnt count as open tab? apologies if it sounded like loaded question , genuinely trying to understand the way it is supposed to worki
    - c-hendricks 3y ago
      Pretty much! IMO Safari is the only browser that gets Pinned Tabs right. In Safari, when you pin a tab, it's available in all your browser windows, and cannot be closed (if you do close it, it comes right back). To remove them, you have to manually unpin the tab. There's also only ever one "instance" of the tab taking up resources, no matter how many windows you have open, even if that tab is selected (the other windows open to that tab darken). Also, if you manually navigate in another tab to the URL of one of your pinned tabs, it switches to the pinned tab. Also, if you have a pinned tab selected and type in a new url, it will open a new tab instead of changing your pinned tab. Compared to Chrome / Edge, where a pinned tab: - is only available in the window you pin it in - closes with the keyboard shortcut to "close all tabs" I've never found any use to that implementation. In those browsers it's more like "make this tab small and place it to the left"

“Should” is doing a lot of work in this sentence. It very much should not do this, if it’s following normal AppKit conventions. Might be a nice optional feature request…

sitzkrieg 3y ago

where is pinned vs normal tab treatment for closing in appkit conventions?

c-hendricks 3y ago
This seems pedantic. Pinned Tabs can be considered like an entry in your bookmark bar. Yes, they're in a different place, but they're a button in the UI, in all windows of the browser, that takes the user to a URL. What's going on here is the user is closing the last tab in their window and expecting it to stay open.
- sitzkrieg 3y ago
  so to put it more simply, a pinned tab behaves like a button so it doesnt count as open tab? apologies if it sounded like loaded question , genuinely trying to understand the way it is supposed to worki
  - c-hendricks 3y ago
    Pretty much! IMO Safari is the only browser that gets Pinned Tabs right. In Safari, when you pin a tab, it's available in all your browser windows, and cannot be closed (if you do close it, it comes right back). To remove them, you have to manually unpin the tab. There's also only ever one "instance" of the tab taking up resources, no matter how many windows you have open, even if that tab is selected (the other windows open to that tab darken). Also, if you manually navigate in another tab to the URL of one of your pinned tabs, it switches to the pinned tab. Also, if you have a pinned tab selected and type in a new url, it will open a new tab instead of changing your pinned tab. Compared to Chrome / Edge, where a pinned tab: - is only available in the window you pin it in - closes with the keyboard shortcut to "close all tabs" I've never found any use to that implementation. In those browsers it's more like "make this tab small and place it to the left"