Add settings to continue/stop when page closes/URL changes
Repository details (talkie)
- Project page
- talkie
- Project log category
- talkie (708 entries)
- Repository
- @joelpurra/talkie
- Owner
- @joelpurra
- Issues
- Issues on Github
- Contributors
- Contributors on Github
- Project status
- ⏲️ This project has had recent commits.
- 📂 This project is open.
- 🌠 This project is popular.
- Repository activity period
- 🗓—
- Commits
- 751 commits
- Stars
- 72 stars
Commit details (9f30d80c)
- Author
- Joel Purra
- Authored at
- Committer
- Joel Purra
- Committed at
Commit message
Add settings to continue/stop when page closes/URL changes
- When selecting page text for speaking, using the Talkie browser button or corresponding keyboard shortcut, the "speaking tab" (id number) is stored.
- Does not apply for text which does not have a tab context, such as (context menu-triggered) selected text or text from the clipboard.
- Before this commit, Talkie always stopped reading (or attempted to) when the "speaking tab" (or window) was closed or the URL changed.
- The behavior is inconsistent across websites and browsers.
- Websites can script-trigger URL changes, with or without user interaction, stopping speech. This includes navigating menus or scrolling on infini-scroll pages.
- Firefox does not trigger events (or include all event data) for (all) URL changes, meaning that speech does not stop. This is due to privacy concerns, even with the
activeTabpermission.- Introducing two settings, for both tab close and URL change events separately, to either continue or stop.
- The default for all browsers is to stop on tab close.
- The default for Firefox is to continue reading on URL change, consistent with current experienced behavior. All other browsers (Chromium-based) stop by default.
Fixes #45.
Raw text
Add settings to continue/stop when page closes/URL changes - When selecting page text for speaking, using the Talkie browser button or corresponding keyboard shortcut, the "speaking tab" (id number) is stored. - Does not apply for text which does not have a tab context, such as (context menu-triggered) selected text or text from the clipboard. - Before this commit, Talkie always stopped reading (or attempted to) when the "speaking tab" (or window) was closed or the URL changed. - The behavior is inconsistent across websites and browsers. - Websites can script-trigger URL changes, with or without user interaction, stopping speech. This includes navigating menus or scrolling on infini-scroll pages. - Firefox does not trigger events (or include all event data) for (all) URL changes, meaning that speech does not stop. This is due to privacy concerns, even with the `activeTab` permission. - Introducing two settings, for both tab close and URL change events separately, to either continue or stop. - The default for all browsers is to stop on tab close. - The default for Firefox is to continue reading on URL change, consistent with current experienced behavior. All other browsers (Chromium-based) stop by default. Fixes #45.