-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invisible HTML prevents word detection #366
Comments
I wonder if I can give rikaikun the ability to delete content on demand. |
or, automatically excluding hidden elements may work... |
Will skip nodes which are |
Specifically, ignore `display: none` and `visibility: hidden`. Fixes #366
Specifically, ignore `display: none` and `visibility: hidden`. Fixes #366
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: Jasmine + Karma + Headless Chrome. Works with vscode debugging for fast test driven development. Unrelated changes required for compilation: - options.ts my LitToast interface needed to extend `Element` when compiling with karma and tsc. Not sure why it worked with `ts-loader` - I needed to update webpack.config to accept a partial argv since of course we are only using `mode`. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: Jasmine + Karma + Headless Chrome. Works with vscode debugging for fast test driven development. Unrelated changes required for compilation: - options.ts my LitToast interface needed to extend `Element` when compiling with karma and tsc. Not sure why it worked with `ts-loader` - I needed to update webpack.config to accept a partial argv since of course we are only using `mode`. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: Jasmine + Karma + Headless Chrome. Works with vscode debugging for fast test driven development. Unrelated changes required for compilation: - options.ts my LitToast interface needed to extend `Element` when compiling with karma and tsc. Not sure why it worked with `ts-loader` - I needed to update webpack.config to accept a partial argv since of course we are only using `mode`. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. With --coverage flag, we get a coverage report that we can upload to codecov. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. With --coverage flag, we get a coverage report that we can upload to codecov. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. With --coverage flag, we get a coverage report that we can upload to codecov. Fixes #366 Fixes #159
Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. With --coverage flag, we get a coverage report that we can upload to codecov. Fixes #366 Fixes #159
…use (#561) Specifically, ignore `display: none` and `visibility: hidden`. This change is also the first unit tested change so contains the initial configuration of testing. (See #159 for details on decisions). Testing Stack: @web/test-runner + Mocha/Chai/Sinon + Puppeteer Headless Chrome. Works with vscode debugging for fast test driven development. With --coverage flag, we get a coverage report that we can upload to codecov. Fixes #366 Fixes #159
## [2.0.0](v1.2.6...v2.0.0) (2021-07-17) ### ⚠ BREAKING CHANGES * This version includes optional chaining requiring Chrome >=80 ### Features * Force Google Docs to use HTML mode instead of canvas mode ([#596](#596)) ([94b60a6](94b60a6)), closes [#593](#593) * **detection:** Ignore invisible nodes when extracting text under mouse ([#561](#561)) ([cb97f36](cb97f36)), closes [#159](#159) [#366](#366) [#159](#159) ### Bug Fixes * **dict:** Update dictionaries to latest versions. ([#581](#581)) ([77189c3](77189c3)) * Skip text processing when range is null ([#598](#598)) ([ae55bff](ae55bff)), closes [#386](#386) ### Code Refactoring * Migrate from webpack to snowpack for build step ([#583](#583)) ([1bdd3d3](1bdd3d3))
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
rikaikun tries to flatten dom but in this case some weird auxillary hidden text has been added to facilitate some minor mini dictionary. Since they are considered text nodes, even if invisible they interrupt the word.
Part of this is the netflix language extension's poor grammar parsing but we could also try to ignore invisible elements...
The text was updated successfully, but these errors were encountered: