Open yfdyh000 opened 6 years ago
I think embed TTS tool in current page will cause more problem. That means we have TTS tool in every tab, and more limit, for example: https://bugzilla.mozilla.org/show_bug.cgi?id=1310082 We need MODIFY user's web page, handle mouse drag event, etc.
Open TTS tool in new tab, user need switch tabs between TTS tool and web page. Some behavior conflict witch current design, it will be a big code modify. I'm not sure if that is better than current design. Have any idea about that?
If this does not require major changes, providing an option may be good.
I guess an embedded panel does not need too much cost, but I don't have the experience and resources to does this.
You can check the domain and force open a window when the current page is privileged. privacy.resistFingerprinting.block_mozAddonManager
as workaround is available.
The current design is available, I just assume more. For example, a toolbar_button (browser_action) or page_action is also possible, like Search Site add-on.
Enable privacy.resistFingerprinting.block_mozAddonManager
to allow add-on modify mozilla.org sites is a security issue, I hope my user do not need to enable it.
Thanks for your suggestion.
I don't have the experience and resources
If licensing allows, maybe code from one of these extensions can help:
Opens window is slower.