aboutsummaryrefslogtreecommitdiff
path: root/ext/mixed/js
Commit message (Collapse)AuthorAge
* 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
|
* Rename Popup.setVisible to setVisibleOverridetoasted-nutbread2019-10-05
|
* Simplify onWheel handlertoasted-nutbread2019-10-02
|
* Use KeyboardEvent.key for onKeyDown handlerstoasted-nutbread2019-10-02
|
* Merge pull request #230 from toasted-nutbread/edge-fixesAlex Yatskov2019-09-30
|\ | | | | Use toIterable for cross-window origin objects
| * Use toIterable for cross-window origin objectstoasted-nutbread2019-09-29
| |
* | Clean up event listenerstoasted-nutbread2019-09-27
| |
* | Change how current entry is indicatedtoasted-nutbread2019-09-27
| |
* | Remove jQuery calls from adderButtonFind and viewerButtonFindtoasted-nutbread2019-09-27
| |
* | Implement custom window scrolltoasted-nutbread2019-09-27
| |
* | Use raw event listenerstoasted-nutbread2019-09-27
| |
* | Use raw element references for container and spinnertoasted-nutbread2019-09-27
| |
* | Use entryIndexFind without jQuerytoasted-nutbread2019-09-27
|/
* Add option to enable Alt+B lookupodehjoseph2019-09-26
|
* Remove destructuring from searchAt, containsPoint, docRangeFromPointtoasted-nutbread2019-09-14
|
* Add a context object for all calls to fetch optionstoasted-nutbread2019-09-10
|
* Add option for enabling deep scanningtoasted-nutbread2019-09-02
|
* Make the imposter element tracked using TextSourceRangetoasted-nutbread2019-08-31
|
* Merge pull request #188 from toasted-nutbread/edge-supportAlex Yatskov2019-08-28
|\ | | | | Add support for Edge browser
| * Add support for Edge browsertoasted-nutbread2019-08-26
| |
* | Merge pull request #176 from toasted-nutbread/selection-touch-scan-disableAlex Yatskov2019-08-17
|\ \ | |/ |/| Don't scan when touching the current selection