hschimke / browsequeue Goto Github PK

Had the following observations after usability stress testing:

Observation 1: Icon name in button bar is labeled "Queue Control", extension name and all other references are "Browse Queue".
Suggestion 1.1: Ensure both names are consistent so new users are not confused (I was) about which extension is being used. Also, Icon in button bar consistency with icon used everywhere else is rather confusing and perhaps change of icon option would be handy with default being same as ones used for extension on chrome store and extensions page.

Observation 2: Not easy to tell if in quick click mode or normal mode without being in options page or actually clicking on the icon.
suggection 2.1: mouse-over hover text can indicate mode , icon color or different icons for mode. or smal shape next to number of links stored in queue indicating mode.

Suggestion 3: Right click or left click option to bring up a view property list of links stored in current folder and folder name change option from the drop list in this popup view property list.

Thank you.

1. An option to only automatically turn new tabs into queue items when you have more than X many tabs open
2. An option to stop tabs from certain domains from automatically becoming queue items
3. When you enable the tool, then close and reopen Chrome, it is still enabled
4. When you load the next item from the queue, it loads into the frontmost tab, not the tab that you previously used to load the previous next item

I'd roll up my sleeves and have a crack at it bad sadly my experience stretches only to Ruby.

There's something wrong with the manifest.

This isn't an "issue" (the actual program seems to be working fine for me), but I would suggest an auto-advance option (with either a possible time-out detection or set wait period).

As for why someone would use this, I'm currently looking at it for some facebook game websites where they give daily "rewards" upon visiting certain urls.

Once the url is loaded, the player no longer cares what is in that window, and hence goes onto the next one.

It's not a major issue, but it might of interest to a wider group if it does have an auto-load function as well as the simple click or keyboard advance.