From 92cc03affdf52a4a395d47d2c9705ae05002e332 Mon Sep 17 00:00:00 2001 From: matt Date: Wed, 9 Dec 2020 10:47:03 -0700 Subject: [PATCH] todos: cross-browser support and embedded version --- README.md | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 7738e83..f161b15 100644 --- a/README.md +++ b/README.md @@ -91,4 +91,26 @@ This loads the code generated in `./dist` as a chrome plugin. `.eslintrc` and `.eslintignore` are both present. To lint project javascript manually, run `npm run lint` or `$ eslint [--fix] .` under project root. -We also have a Github action that runs `eslint --fix .` and commits automatically to enforce formatting. \ No newline at end of file +We also have a Github action that runs `eslint --fix .` and commits automatically to enforce formatting. + +## Todo: embedded version + +Goal: + +so that website maintainers can include this one liner in their HTML and get click-in-text on their page: + + `` + +Question: + +Do we need an option/configuration page in this embedded version? Current chrome extension supports configuration by +a chrome proprietary menu, where you can set things like `translation delay`, `translation key - alt/ctrl`, `hover or click` etc. + +If we do need a option page for embedded version, in what form do we present the options page? I think a hovering widget +is ideal. + + +## Todo: Adapt to multiple browsers + +Seems like there are ways to write a cross-browser extension in one codebase, +see more at Mozilla's [Build a cross browser extension](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Build_a_cross_browser_extension) \ No newline at end of file