3 ms·
In my case, users need to switch back and forth between multiple tables often (maintaining things like state and scroll position). So if I don't leverage browse
by thomasrognon 6y ago
In my case, users need to switch back and forth between multiple tables often (maintaining things like state and scroll position). So if I don't leverage browser tabs, I'll have to implement tabbing within the app. Of course, users could still choose to open tables in new tabs also, but that would result in two levels of tabbing.
- zzo38computer 6y agoWell, what I am trying to say is that if you do it properly then you will not have to consider that, since it will already work. If they user wants to open a new tab, they can middle click (or whatever other method is correct for doing so on their browser, which might not be middle click); if not, they can left click (or tab to it and push enter, or whatever). For state and that stuff is a valid point, but if the browser history and the URLs in the browser history should generally be able to store whatever such things are valid, I think. It isn't browser tabs that are confusing, but rather when you try to override the existing user interface with your own, that makes it confusing and difficult to work with.
- tdeck 6y agoCan you create some variation in the tab icons so it's easier to find the one you were just looking at? I've never seen this done but I do often have the problem of having, say, 10 Google Docs open in a full tab bar and not knowing which is which.
- thomasrognon 6y agoI really like this idea. I already planned on enabling users to upload thumbnails images for the "book cover" of a table. I could make each tab's favicon based on that.