This is what Chrome mobile looks like it you have 100+ tabs.
-
-
:D
-
:D
-
@Weng E_NO_REPRO_CHROME_TABLET_MODE
Edit: Censorship
-
@Tsaukpaetra that looks like 3 tabs, not 100+
Oh, my bad, the rest are stacked behind the first. Interesting.
-
...why do you have 100+ tabs on Chrome?
Also your phone has an update! Update your phone!
-
@Kian said in This is what Chrome mobile looks like it you have 100+ tabs.:
@Tsaukpaetra that looks like 3 tabs, not 100+
Oh, my bad, the rest are stacked behind the first. Interesting.Yeah, and closing the fuckers takes longer than opening them, because a mis-click focuses them, which causes a pause while it reloads.
And since there's no "opened tabs count" I probably had more like 200, so closing them back again took.... time...
-
@anonymous234 said in This is what Chrome mobile looks like it you have 100+ tabs.:
...why do you have 100+ tabs on Chrome?
Also your phone has an update! Update your phone!
Rooted so I need to apply them manually.
As for why... Closing tabs is work.
-
@Tsaukpaetra said in This is what Chrome mobile looks like it you have 100+ tabs.:
Yeah, and closing the fuckers takes longer than opening them, because a mis-click focuses them, which causes a pause while it reloads.
I had some game on my tablet with a link to the developer's site that opened in Chrome. If you misclicked it while not on wifi, you'd get the usual Chrome error page, but it would then try to open the page in another tab. Which would error out and then try again in another tab. The fuckers were opening faster than I could close them, it locked it up so much I couldn't open the multi tasking view to close Chrome, and even when I did they were still there when I opened it again. Without connecting back to wifi, the only option I'd have had would be to clear all Chrome data from the apps settings window. As it was, I got on wifi and spent a good 10-15 minutes closing tabs
-
@Jaloopa said in This is what Chrome mobile looks like it you have 100+ tabs.:
If you misclicked it while not on wifi, you'd get the usual Chrome error page, but it would then try to open the page in another tab.
Well of course it did! There's a chance the next tab is so much further to the side that it has wifi reception ;)