You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the chrome extension (1.1077.0.0 (Official Build)) and perhaps I'm doing something wrong but it seems that every time I navigate to a new site (on which I have to enable the Hypothesis extension and log back into it) the group I'm now making annotations under is my generic, default public group. After making several annotations relevant to whatever project I'm working on, I realize they're not being made in that project's group. (There also seems to be no way to edit an annotation's group after it's been saved for the first time? But I could be just missing how to do that.) In any case I then have to re-create my annotations in the correct project group, which is causing some extra work and a bit of frustration, particularly because even though this has happened a dozen times I still forget to change the group every single time.
I should, I suppose, be able to remember to change the group every time I go to a new page, but repetitive tasks like this seem like prime targets for reducing the need for user intervention. For my workflow at least It would be preferable to 1) have the plugin default to the last group under which an annotation was made when annotating on a new page, since I don't often switch between groups multiple times in one sitting. If not possible, something similar could be accomplished if the plugin would 2) allow the user to re-order their groups so that the current one they're working on will be the top (and presumably the new default?) group when going to a new page, or to otherwise allow the user to manually set the current default group. Even though the latter option requires changing the default when changing projects, it at least is a single change and not required on each new page.
The text was updated successfully, but these errors were encountered:
I guess I should have more thoroughly read the open issues rather than searching them for what I thought was my specific issue. After making the changes suggested in #484 I no longer have to log in on each new page, and based on a couple quick tests my most recently used group appears to be still selected.
I still wouldn't mind the ability to re-order groups so they're not constrained to simple alphabetical listing, but the major pain point appears to be solved!
on which I have to enable the Hypothesis extension and log back into it)
It sounds like you have third-party cookies blocked, which also interferes with Hypothesis's ability to persist certain settings and login state between different websites.
The solution for the Chrome extension will be to avoid relying on the "standard" local storage that iframes have access to and instead store those settings in extension-specific storage, which we can persist even if third-party cookies are blocked.
I'm using the chrome extension (1.1077.0.0 (Official Build)) and perhaps I'm doing something wrong but it seems that every time I navigate to a new site (on which I have to enable the Hypothesis extension and log back into it) the group I'm now making annotations under is my generic, default public group. After making several annotations relevant to whatever project I'm working on, I realize they're not being made in that project's group. (There also seems to be no way to edit an annotation's group after it's been saved for the first time? But I could be just missing how to do that.) In any case I then have to re-create my annotations in the correct project group, which is causing some extra work and a bit of frustration, particularly because even though this has happened a dozen times I still forget to change the group every single time.
I should, I suppose, be able to remember to change the group every time I go to a new page, but repetitive tasks like this seem like prime targets for reducing the need for user intervention. For my workflow at least It would be preferable to 1) have the plugin default to the last group under which an annotation was made when annotating on a new page, since I don't often switch between groups multiple times in one sitting. If not possible, something similar could be accomplished if the plugin would 2) allow the user to re-order their groups so that the current one they're working on will be the top (and presumably the new default?) group when going to a new page, or to otherwise allow the user to manually set the current default group. Even though the latter option requires changing the default when changing projects, it at least is a single change and not required on each new page.
The text was updated successfully, but these errors were encountered: