News for hackers. Stuff that matters.
Re:Google proposes changes to Chromium which would disable u... by albru123 on Tuesday January 22, 2019 @06:29PM (#18973904)
Firefox does not stack tabs like Chrome does and does not load all the restored session tabs at once either. Aren't these dumb design decisions enough to switch to a product where people actually think about how it's going to be used?
Re:Google proposes changes to Chromium which would disable u... by Arelius on Tuesday January 22, 2019 @06:58PM (#18974191)
> does not load all the restored session tabs at once either

As someone who always has too many tabs open, I consider this a plus.

I do however think you can disable this in about:config : browser.sessionstore.restore_on_demand

Re:Google proposes changes to Chromium which would disable u... by Zardoz84 on Wednesday January 23, 2019 @02:18AM (#18976364)
also, if you use Autodiscard plugin, you will find that FF use less RAM and Ru. more faster. Essentially discard and suspend tabs that you aren't using.
Re:Google proposes changes to Chromium which would disable u... by jinnko on Tuesday January 22, 2019 @06:45PM (#18974059)
Laying all the trans at one cripples my core i8 system for some time. Firefox's lazy tab loading is a much better user experience. Together with TreeStyle Tabs and the recent multi-container add-on, Firefox is just a better experience.
Re:Google proposes changes to Chromium which would disable u... by zcid on Tuesday January 22, 2019 @07:16PM (#18974342)
I used to be a fanatic about tree style tabs, but due to the new api, it's unusable with containers. I recently switched over to vertical tabs for that reason. I miss the tree layout, but at least now my tabs maintain their ordering.
Re:Google proposes changes to Chromium which would disable u... by Nullabillity on Wednesday January 23, 2019 @05:48AM (#18977216)
All of my TST issues have been related to the layout cache. You can disable it if you right-click the toolbar icon.
Re:Google proposes changes to Chromium which would disable u... by zcid on Wednesday January 23, 2019 @09:45AM (#18978495)
Thanks for the heads up. I'll play around with it sometime later this week. I would love to have it working consistently again.
Re:Google proposes changes to Chromium which would disable u... by Izkata on Wednesday January 23, 2019 @08:34AM (#18977923)
What are you talking about? I've been using TreeStyleTabs with containers for a good year or so.
Re:Google proposes changes to Chromium which would disable u... by zcid on Wednesday January 23, 2019 @09:43AM (#18978472)
I'm sure you're aware that not every user will have the same experience with a piece of software. There are a couple of bugs referenced in the Github issues for TST relevant to containers. There is a workaround, but I experience the issue again within a half hour. Not worth it to me.
Re:Google proposes changes to Chromium which would disable u... by Izkata on Wednesday January 23, 2019 @01:58PM (#18981401)
Alright, it's just that the phrasing - blaming it on the new API - made it sound like an inherent flaw that would affect everyone, which definitely isn't right.
Re:Google proposes changes to Chromium which would disable u... by teraflop on Tuesday January 22, 2019 @06:42PM (#18974031)
> and does not load all the restored session tabs at once either

For what it's worth, Chrome stopped doing this for me in a recent update (I think version 71).

Re:Google proposes changes to Chromium which would disable u... by stuartd on Tuesday January 22, 2019 @06:52PM (#18974127)
.. and Chrome doesn't have container tabs, which for me are a killer feature.