aboutsummaryrefslogtreecommitdiff
path: root/ext/mixed/js
Commit message (Collapse)AuthorAge
* use fallback for ambiguous furiganasiikamiika2019-11-27
| | | | fixes #281, fixes #94
* Organize core.jstoasted-nutbread2019-11-26
|
* utilIsObject => isObject, move to core.jstoasted-nutbread2019-11-26
|
* Rename extension.js to core.js to better reflect its usetoasted-nutbread2019-11-26
|
* Update how source terms are navigatedtoasted-nutbread2019-11-26
|
* Require context for setContentTerms and setContentKanjitoasted-nutbread2019-11-26
|
* Merge pull request #279 from siikamiika/query-parser-1siikamiika2019-11-26
|\ | | | | Search page query parser
| * add reading modessiikamiika2019-11-23
| |
| * give names to complex slicessiikamiika2019-11-23
| |
| * remove unneeded featuresiikamiika2019-11-23
| | | | | | | | Unidic actually has a field for the base form of the input
| * add mecab supportsiikamiika2019-11-23
| |
| * fix default params for term clickingsiikamiika2019-11-23
| |
| * add kana to textsiikamiika2019-11-23
| |
| * add simple query parsersiikamiika2019-11-23
| |
* | Replace string.substr and string.slice with string.substringtoasted-nutbread2019-11-24
|/ | | | Improves semantic clarity, and it's recommended to not use substr.
* Merge pull request #274 from toasted-nutbread/lookup-wildcardsAlex Yatskov2019-11-13
|\ | | | | Lookup wildcards
| * Add details field to apiTermsFindtoasted-nutbread2019-11-10
| |
* | only paste Japanese text from clipboardsiikamiika2019-11-13
|/
* Create functions for the cases of isMouseButtontoasted-nutbread2019-11-10
| | | | | | | | | | | | | | jshint was showing a warning that there was no break statement after the first case, which there doesn't need to be. The most straightforward way to fix this without using the unclear // jshint ignore:line is to just have two functions. This change also updates invocations of isMouseButton to use the exact case function, as this will remove the need to check the case of mosueEvent.type. This was done because onMouseMove is invoked at a high frequency.
* Fix overwriting const valuetoasted-nutbread2019-11-10
|
* Fix several warnings about name conflictstoasted-nutbread2019-11-10
|
* Use for of loop instead of forEachtoasted-nutbread2019-11-10
|
* Remove Download check when resolving Audio datasabs2019-11-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a bug (seemingly unreported) in Yomichan where an Anki card will not contain any audio if the JapanesePod101 audio source trumps a secondary audio source (e.g. JapanesePod101-alternate) where the jpod101 source can't find the word requested. For example, そして has an audio entry in the alternate source but not the standard source. (Alternatively, there may be a bug in the jpod101 audioUrlBuilder, because I've only noticed this problem with hiragana-only expressions. JPod101 may not host those on the same url scheme any more. I'm not sure how to fix that, though, and the bug I'm addressing here does still persist). The reason this happens is that audioGetFromUrl uses downloaded audio to effectively check for a 404 (by examining the audio duration), but that check doesn't happen when an Anki card is being created (i.e. "download" is set, which I've changed to "willDownload" here). This change removes that check, but retains the will-download intent information to prevent attempts to download tts data, which AnkiConnect cannot do. I've also added a short explanation as to why the download check happens where it does. I think the unused audio object will get garbage collected since it's not referenced again, but I've explicitly unset it as well.
* Optimize dictFieldFormattoasted-nutbread2019-11-08
|
* refactoring and optimizationsiikamiika2019-11-04
|
* prevent accidental lookup on glossary text selectsiikamiika2019-11-03
|
* Create promise version of setTimeouttoasted-nutbread2019-10-28
|
* 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
* Make the search button reuse an open search tab if it existstoasted-nutbread2019-10-19
|
* Update *show* APIs to unified showContent and setContenttoasted-nutbread2019-10-17
|
* Add support for text-to-speech playbacktoasted-nutbread2019-10-13
|
* Rename audioGetFromSources's createAudioObject argument to downloadtoasted-nutbread2019-10-13
|
* Add option for text-to-speechtoasted-nutbread2019-10-13
|
* Update how custom CSS is appliedtoasted-nutbread2019-10-12
|
* Create themestoasted-nutbread2019-10-12
|
* Remove Display.dependenciestoasted-nutbread2019-10-12
|
* Don't pass options around for calls to termsShow, kanjiShow, etc.toasted-nutbread2019-10-12
|
* Check if objects are properly initialized before showing contenttoasted-nutbread2019-10-12
|
* Update Display initialization processtoasted-nutbread2019-10-12
|
* Add function for (de)activating event listeners in Displaytoasted-nutbread2019-10-12
|
* Update title with info about what the audio source wastoasted-nutbread2019-10-10
|
* Implement audio fallbackstoasted-nutbread2019-10-10
|
* Update audio options formattoasted-nutbread2019-10-10
|
* Pass optionsContext to audioBuildUrl handlerstoasted-nutbread2019-10-09
|
* Show the viewer button for anki notes which already existtoasted-nutbread2019-10-09
|
* Create utility function for logging errorstoasted-nutbread2019-10-08
|
* Update rejections to use Errortoasted-nutbread2019-10-08
|
* Throw Error instead of stringtoasted-nutbread2019-10-08
|
* Validate that key is a stringtoasted-nutbread2019-10-08
| | | | On Chrome, when clicking an autocomplete dropdown menu option, a keydown event is generated which is not of type KeyboardEvent.
* Update how popup visibility workstoasted-nutbread2019-10-05
|