aboutsummaryrefslogtreecommitdiff
path: root/ext/mixed/js/display.js
Commit message (Collapse)AuthorAge
* Update how spinner visibility is controlledtoasted-nutbread2020-01-16
|
* Update display content generation to use HTML templatestoasted-nutbread2020-01-16
|
* Update license info URLtoasted-nutbread2020-01-01
|
* Update copyrighttoasted-nutbread2020-01-01
|
* Move optionsUpdate message handler into Yomichan classtoasted-nutbread2019-12-20
|
* Simplify options passed to docRangeFromPointtoasted-nutbread2019-12-17
|
* Update display key handlerstoasted-nutbread2019-12-13
|
* Update display message handlerstoasted-nutbread2019-12-13
|
* navigate history with wheel only over buttonssiikamiika2019-12-07
|
* fix serialization errors on Chromesiikamiika2019-12-04
|
* Merge pull request #291 from toasted-nutbread/cloze-fixesAlex Yatskov2019-12-03
|\ | | | | Cloze fixes
| * Simplify clozeBuildtoasted-nutbread2019-11-26
| |
| * Update cloze.body to use original sentence texttoasted-nutbread2019-11-26
| |
| * Pass kanji character to clozeBuildtoasted-nutbread2019-11-26
| |
* | fix entry scroll index 0 bugsiikamiika2019-12-01
| | | | | | | | | | Introduced in 4e7d08ff2c184a361622a6efaf00e21af51428a9 because the range-limited index value isn't kept in the same scope.
* | always update current position on term lookupsiikamiika2019-12-01
| |
* | move Display context to a new classsiikamiika2019-12-01
| |
* | remove dead codesiikamiika2019-11-30
| |
* | rewrite history as a doubly linked listsiikamiika2019-11-30
| |
* | fix context type inconsistenciessiikamiika2019-11-29
| |
* | 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
|