aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Fix overlapping popup timerstoasted-nutbread2019-11-05
|
* refactoring and optimizationsiikamiika2019-11-04
|
* prevent accidental lookup on glossary text selectsiikamiika2019-11-03
|
* Fix autoHideResults not workingtoasted-nutbread2019-11-03
|
* Add faviconstoasted-nutbread2019-11-02
|
* Force LF line endings for template filestoasted-nutbread2019-10-28
|
* Group similar functions togethertoasted-nutbread2019-10-28
|
* Fix some issues with the context menutoasted-nutbread2019-10-28
|
* Style updatetoasted-nutbread2019-10-28
|
* Reset preventions earliertoasted-nutbread2019-10-28
|
* Check pendingLookup earliertoasted-nutbread2019-10-28
|
* Remove setPrimaryTouchtoasted-nutbread2019-10-28
|
* Simplify touch event implementationtoasted-nutbread2019-10-28
|
* Make selectionContainsPoint statictoasted-nutbread2019-10-28
|
* Improve namingtoasted-nutbread2019-10-28
|
* Remove setterstoasted-nutbread2019-10-28
|
* Remove unused variabletoasted-nutbread2019-10-28
|
* Remove searchFromTouchtoasted-nutbread2019-10-28
|
* Simplify how touch events use onAfterSearchtoasted-nutbread2019-10-28
|
* Rename textSourceLast to textSourceCurrenttoasted-nutbread2019-10-28
|
* Update how definitions are searched fortoasted-nutbread2019-10-28
|
* Move checktoasted-nutbread2019-10-28
|
* Remove unused varstoasted-nutbread2019-10-28
|
* Don't pass null textSource into searchSourcetoasted-nutbread2019-10-28
|
* Use promiseTimeouttoasted-nutbread2019-10-28
|
* Move onError catch into searchAttoasted-nutbread2019-10-28
|
* Create promise version of setTimeouttoasted-nutbread2019-10-28
|
* improve search page checkbox usabilitysiikamiika2019-10-28
| | | | | Disable text selection and make the entire area clickable, including whitespace
* refactoringsiikamiika2019-10-28
|
* fix wanakana toggle on empty inputsiikamiika2019-10-27
|
* use apiOptionsGet to modify the correct profilesiikamiika2019-10-27
|
* Revert "modify correct profile apiOptionsSet"siikamiika2019-10-27
| | | | This reverts commit 51c35c9f306e48093fc769713675dca5b02d1398.
* modify correct profile apiOptionsSetsiikamiika2019-10-27
|
* make search page checkbox options persistsiikamiika2019-10-27
|
* add workaround to Chrome clipboard.readTextsiikamiika2019-10-27
| | | | | For some reason this doesn't work on Firefox, so keep using the new API for Firefox
* make clipboardRead an optional permissionsiikamiika2019-10-27
|
* refactor and tune wanakana togglingsiikamiika2019-10-27
|
* simplify search history state handlingsiikamiika2019-10-26
|
* add button to enable/disable wanakana IMEsiikamiika2019-10-26
|
* keep url query in historysiikamiika2019-10-26
|
* add clipboard monitor to search pagesiikamiika2019-10-26
| | | | Related to issue #262 about APIs
* remember search historysiikamiika2019-10-26
|
* ignore more keys on search pagesiikamiika2019-10-26
|
* focus and scroll to input only when it's neededsiikamiika2019-10-26
|
* tweak ignored keys on search pagesiikamiika2019-10-26
|
* fix various unwanted focus issues on search pagesiikamiika2019-10-26
| | | | Don't focus input if a modifier or specific keys are pressed
* make non-hotkey keys focus input on search pagesiikamiika2019-10-26
| | | | | | | | | | | | | | | | | | The issue was that scanning on search page introduced a way to lose focus of the query input, and the new feature that the search page hotkey focuses an existing search page instead of opening a new one made it more obvious. Now every key that isn't a hotkey focuses the query input, and typing text into the box scrolls it into view in case it wasn't there when searching. There is an accessibility issue that this can cause, because now tab also focuses the query input before it focuses the next element. I didn't implement a workaround for that because it would have been more complicated than this simple fix. Fixes #263
* Merge pull request #265 from Rapptz/patch-1siikamiika2019-10-24
|\ | | | | Proper spacing for Anki in {furigana-plain}
| * Proper spacing for Anki in {furigana-plain}Danny2019-10-23
|/ | | | | | This should fix #264 Note it does not address broken segmentation, just representation within Anki itself to work properly.
* Use chrome.runtime.getURL instead of chrome.extension.getURLtoasted-nutbread2019-10-22
|