Open jerodsanto opened 10 years ago
zachleat
commented
10 years ago Just for future reference, this extension is using a pageAction button instead of a browserAction button. Page action buttons are only displayed for some URLs (in the address bar) and Browser Action buttons are always displayed (in the browser chrome).
If you remove the autojump thing I will be sad. :) But I agree that an always-present button is more intuitive UX for new users.
jmhobbs
commented
10 years ago I don't know if switching back to browserAction is something we should do.
Configuration is a relatively rare event, navigation is fairly common, and single click nav is extremely useful.
This is an expert tool. Someone using this needs to already understand how domains work, and probably has a competent command of their browser. I'm not saying this excuses "hard" configuration, but it certainly weighs heavier when considering convenience of more common access patterns.
I'm not saying we can't figure something out, I just think we should be careful about overly favoring configuration.
jerodsanto
commented
10 years ago Good points. I will probably be configuring more than an average user, but swapping will still be the primary access pattern for me too.
Another thought: what if we switch to the browserAction button but it works just like the current pageAction button when the current domain is in a set. If it's not in a set then the button just takes you to the options screen.
That would help those who just installed the extension know how to configure it and wouldn't sacrifice the single-click swap or require any new UI elements.
This seems like a nice compromise to me.
(Also the current button stomps/overlays my one other pageAction button (Feedbin) when they are both active on a page)
I don't love the experience of having to edit the domain sets from the extension's options page. I realize this extension is for devs and we know how to do that stuff, but it is still a pain and not obvious at all when you install the extension that anything has even happened.
What I'd prefer is if the DomainSwap icon was unconditionally present in the menu bar with the other extensions. When you click it:
A) if the current domain is not in a Set, you are prompted to either add it or create a new Set.
B) if the current domain is in a Set, it shows the switch dialog with an "edit" button of some kind to let you modify/delete the current domain Set.
This removes the ability to auto-jump back and forth between two domains with a single click, but maybe we could facilitate that via a click-and-hold or something.
This is a pretty big request and I can live with it as is, but I'm just throwing it out there in case others think it's a good change and worth the effort.