aboutsummaryrefslogtreecommitdiff
path: root/ext/mixed/js/display.js
Commit message (Collapse)AuthorAge
* clear Display history on new lookupsiikamiika2019-11-28
|
* correct X scroll direction for history navigationsiikamiika2019-11-28
|
* preventDefault correctlysiikamiika2019-11-28
|
* store popped context history in Displaysiikamiika2019-11-28
|
* set current entry even when disableScroll is truesiikamiika2019-11-28
|
* fix scroll issues in Display.entryScrollIntoViewsiikamiika2019-11-28
| | | | | | - Save scroll context before scrolling to top - Explicit null check for scroll param to handle scrolling to y=0 correctly
* Update unused argumentstoasted-nutbread2019-11-26
|
* Use single quotestoasted-nutbread2019-11-26
|
* Replace hasOwnProperty with simplified hasOwn functiontoasted-nutbread2019-11-26
|
* Move additional utility functions to DOMtoasted-nutbread2019-11-26
|
* Update how source terms are navigatedtoasted-nutbread2019-11-26
|
* Require context for setContentTerms and setContentKanjitoasted-nutbread2019-11-26
|
* fix default params for term clickingsiikamiika2019-11-23
|
* add kana to textsiikamiika2019-11-23
|
* add simple query parsersiikamiika2019-11-23
|
* Add details field to apiTermsFindtoasted-nutbread2019-11-10
|
* 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 several warnings about name conflictstoasted-nutbread2019-11-10
|
* Use for of loop instead of forEachtoasted-nutbread2019-11-10
|
* refactoring and optimizationsiikamiika2019-11-04
|
* prevent accidental lookup on glossary text selectsiikamiika2019-11-03
|
* 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
|
* 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
|
* 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
|
* 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
|