Synonyms.com 的评价
Synonyms.com 作者: STANDS4
STANDS4 的回应
开发者回应
发布于 1 个月前Umpahpah — our extension requires a Firefox restart after installation. Would you mind trying again?
7 条评价
- Update: Firefox was restarted, but only after new installation it started to work. So far so good, perhaps missing some useful twerks like pop-up option or right click context menu. But it works, I appreciate the feedback and I will certainly give it a try.
A great idea for an extension, unfortunately it does not work (anymore?)开发者回应
发布于 1 个月前Umpahpah — our extension requires a Firefox restart after installation. Would you mind trying again? - Wow! very helpful Addon! and gives a lot of information. I just selected/highlighted a word and I clicked on the extension button/icon on the top toolbar, and a popup window showed up explaining the word i chosen.
Also your website is very well designed and very helpful! 👍
* One suggestion: it would be perfect if when we Right-click our mouse on the selected word, the "context menu" will show up, and we click the icon from there as well. - 评分 4 / 5来自 Firefox 用户 13574684, 6 年前Highlight a word and click the extension icon and voila: synonyms.
(Suggestion/wish: It would be easier to use with a right click context menu option.)开发者回应
发布于 6 年前Thanks for the great feedback! We'll certainly consider adding a right-click context menu option in future versions... - 评分 5 / 5来自 João Vinholi, 7 年前
- 评分 2 / 5来自 grahamperrin, 8 年前After enabling 'Auto check text' for a domain, I see no way to revert to manual.
After disabling for a domain, I see no way to re-enable.
Does not work with the editable field when writing a comment at GitHub.
Workaround:
1. switch from write mode to preview mode
2. re-select the previously selected text
3. reuse the extension
4. revert to write mode.
Tested with Waterfox 56.2.0.31 on FreeBSD-CURRENT.
Enhancement request:
- please make the extension work with the context menu for selected text.
(It's rarely good to _require_ use of the toolbar, or overflow menu.)
Thanks 开发者回应
发布于 8 年前Hi there, we've just fixed this issue -- apologies for the inconvenience. Would you mind giving it another chance?