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 new to submitting issues, but I really like your extension. However, a few things I have noticed:
It would be nice if there was a way I could left click on the extension for "options" or "settings".
After registering (loading) "free dictionary data", upon opening settings, the data is unalterable and irremovable (even after clicking "reset to default") and is, therefore added to subsequent dictionary files loaded.
It would also be nice if there was an example TSV, JSON, etc. file embedded into the docs as a reference for custom formatting.
The loading symbol for registering data glitches.
Thank you! This is the first time I've submitted an Issue for any project on GitHub. Tell me if I'm missing anything.
The text was updated successfully, but these errors were encountered:
After registering (loading) "free dictionary data", upon opening settings, the data is unalterable and irremovable (even after clicking "reset to default") and is, therefore added to subsequent dictionary files loaded.
Unfortunately, data deletion feature is not supported due to some technical testriction (#51)
It would also be nice if there was an example TSV, JSON, etc. file embedded into the docs as a reference for custom formatting.
I'm new to submitting issues, but I really like your extension. However, a few things I have noticed:
It would be nice if there was a way I could left click on the extension for "options" or "settings".
After registering (loading) "free dictionary data", upon opening settings, the data is unalterable and irremovable (even after clicking "reset to default") and is, therefore added to subsequent dictionary files loaded.
It would also be nice if there was an example TSV, JSON, etc. file embedded into the docs as a reference for custom formatting.
The loading symbol for registering data glitches.
Thank you! This is the first time I've submitted an Issue for any project on GitHub. Tell me if I'm missing anything.
The text was updated successfully, but these errors were encountered: