aboutsummaryrefslogtreecommitdiff
path: root/ext/settings.html
diff options
context:
space:
mode:
authortoasted-nutbread <toasted-nutbread@users.noreply.github.com>2022-09-24 22:44:40 -0400
committerGitHub <noreply@github.com>2022-09-24 22:44:40 -0400
commit8240482e9d0b6da7a996bc581c9b5304ebcf22aa (patch)
tree4d1621193b9990f6cb710a72f9b761aa2b471de6 /ext/settings.html
parentda52caa15247f82377e5d914306de1713ed63cea (diff)
Google Docs accessibility update (#2235)
* Update Google Docs injection script * Create GoogleDocsUtil * Update Frontend.js to register GoogleDocsUtil's getRangeFromPoint handler * Update setting name and description * Add comment * Fix Firefox support
Diffstat (limited to 'ext/settings.html')
-rw-r--r--ext/settings.html14
1 files changed, 8 insertions, 6 deletions
diff --git a/ext/settings.html b/ext/settings.html
index dc1405de..1b5e4fd6 100644
--- a/ext/settings.html
+++ b/ext/settings.html
@@ -2067,7 +2067,7 @@
<div class="settings-item-inner">
<div class="settings-item-left">
<div class="settings-item-label">
- Force HTML-based rendering for Google Docs
+ Enable Google Docs compatibility mode
<a tabindex="0" class="more-toggle more-only danger-text" data-parent-distance="4">(?)</a>
</div>
</div>
@@ -2077,14 +2077,16 @@
</div>
<div class="settings-item-children more" hidden>
<p>
- Google Docs is moving from HTML-based rendering to
+ Google Docs now uses
<a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/canvas" target="_blank" rel="noopener noreferrer">canvas-based</a>
- rendering to display content<sup><a href="https://workspaceupdates.googleblog.com/2021/05/Google-Docs-Canvas-Based-Rendering-Update.html" target="_blank" rel="noopener noreferrer">[2]</a></sup>,
- which prevents Yomichan from being able to scan text.
- Enabling this option will force HTML-based rendering to be used.
+ rendering to display content<sup><a href="https://workspaceupdates.googleblog.com/2021/05/Google-Docs-Canvas-Based-Rendering-Update.html" target="_blank" rel="noopener noreferrer">[2]</a></sup>
+ which prevents Yomichan from being able to scan text using the standard methods.
+ Enabling this option will force Google Docs webpages to expose some additional text
+ information which should allow Yomichan to still work.
</p>
<p class="danger-text">
- This is a workaround and it is likely that Google will unfortunately remove support for this workaround in the future.
+ Google has changed this compatibility implementation several times, and the changes do not seem to be announced or documented.
+ Therefore, it is possible that this feature could stop working at any time the future without warning.
</p>
<p>
<a tabindex="0" class="more-toggle" data-parent-distance="3">Less&hellip;</a>