| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Use ES modules
- Remove vendored libs and build them from npm using esbuild
- Switch from JSZip to zip.js
|
| | |
|
| |\
| |
| |
| | |
search.html clipboard monitor, Anki add note Playwright tests
|
| | |
| |
| |
| |
| |
| | |
prep tests for cicd
reorganize exports in playwright utils
|
| | |
| |
| |
| | |
this is the only blocker to Firefox for Android.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
firefox was previously unable to use declarativeNetRequest, as some
browser state (ExtensionDNRStore) wasn't correctly initialized wrt
yomitan's use of the DNR API. this bug manifested as an unexpected
error on calls to updateDynamicRules(), specifically after the browser
has been restarted.
switching to the use of session rules instead of dynamic rules fixes
this bug. i have tested audio info requests (custom JSON, JPod
Alternate, Jisho) that exhibited the bug after browser restart on
version 115 and 118, and the audio plays instead of the request
failing.
webRequest can now be entirely removed.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
| |
`webRequest` is used on Chrome/MV3 to surface error information from
failed requests. it was added back to the declarative path by
toasted-nutbread in FooSoft/yomichan#2161, but the permissions
documentation did not reflect `webRequests` continued necessity.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
implement getImage for offscreen requests
move offscreen files, offscreen prep is done in sw prep
update permissions document for offscreen
rearrange permissions
|
| |
|
|
| |
on chromium, backend calls to clipboardGet are forwarded to an offscreen script
|
| | |
|
| |
|
|
|
|
| |
* Dynamically set version as argument to build script
* Set version using tag ref_name in CI
* [Cleanup] gitignore ext/manifest.json as it's dynamically generated
|
| |
|
|
|
|
|
|
| |
`declarativeNetRequest.updateDynamicRules()` returns with an
unexpected error in Firefox, but only after the browser has been
restarted. On a fresh install of Yomitan it works, causing bug
flakiness. `declarativeNetRequest` can be disabled in the manifest as
a workaround.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Firefox added the scripting API in 102. This should fix the majority
of warnings listed in #96:
- insertCSS
- executeScript
- getRegisteredContentScripts
- contentScripts.register
- registerContentScripts
- unregisterContentScripts
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
* Fix ajv validation errors
* Update error format
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* Create new StringUtil
* Use StringUtil in DOMTextScanner
* Fix order
|
| | |
|
| |
|
|
|
|
|
| |
* Add support for not building a zip
* Update gitignore
* Add safari variant
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Generalize _onBeforeSendHeadersAddListener
* Simplify filter assignment
* Use requestId rather than done
* Properly support Firefox addListener without arguments
* Add details to fetchAnonymous errors
* Refactor
* Enable support for no header modifications
* Update MV3 support for error details
* Expose errors in downloadTermAudio
* Throw an error if audio download fails due to potential permissions reasons
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Install eslint-plugin-jsdoc
* Initial rules setup
* Update lists
* Use @returns rather than @return
* Remove error throwing code which is never executed
* Fix issues relating to @throws
* General error fixes
* Update Display type documentation
* Various doc fixes
* Fix invalid tuple syntax
* Doc updates
* Remove unused
* Doc updates
* Enable jsdoc/require-returns
* Update rules
* Update remaining rules
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Update build-libs.js
* Add a test for build-libs.js
* Update parse5
* Rebuild parse5
* Update build-libs.js to generate consistent path names
* Rebuild
|
| |
|
|
|
|
|
|
|
| |
* Reuse JsomSchema instance
* Install ajv
* Add support for using ajv as a JSON schema validator
* Update usage
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add support for structured content lists and `list-style-type` style
A full list of supported style types is documented here:
https://developer.mozilla.org/en-US/docs/Web/CSS/list-style-type
There's nothing in this code preventing a term bank from assigning,
for example, a `list-style-type` style to a `div` element, but it
doesn't seem like browsers will complain about things like that.
* Add support for `lang` attribute in structured content
Support added for the following node types:
"ruby", "rt", "rp", "table", "thead", "tbody", "tfoot", "tr", "td",
"th", "span", "div", "ol", "ul", "li", "a"
I couldn't get it to work for the alt-hover text on "img" tags.
Tests are included in the file
"test/data/dictionaries/valid-dictionary/term_bank_1.json"
* Add styles for structured content lists
* Add override rules for new structured-content list styles
see: https://github.com/FooSoft/yomichan/pull/2129
Co-authored-by: stephenmk <stephenmk@users.noreply.github.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Change siteColor to siteTheme
* Fix potential null exception
* Simplify
* Update display theme assignment
* Add a data-browser-theme attribute
* Add "browser" option for theme
* Create ThemeController
* Add theme-controller.js to relevant pages
* Use ThemeController
* Simplify
* Fix 'light' being used instead of 'default'
* Update the settings values to more accurately reflect their usage
* Change default site theme in display.js
* Remove async
* Restore async for consistency
|