read-aloud icon indicating copy to clipboard operation
read-aloud copied to clipboard

Not functioning inside of Flatpak sandbox

Open robert2343 opened this issue 3 years ago • 5 comments

I am running Librewolf (fork of Firefox), which I installed from Flatpak on Linux Mint (which is why it is in a sandbox), and I am trying to use the Google Translate English option, and every time I try to read anything aloud, it says "click here to start", and when I click there, that message goes away, then reappears after about a second. I get no sound. It works on normal Firefox, installed by default on my distribution. Does anyone know how to fix this or atleast something that Read Aloud uses that would be made unavailable by a sandbox?

robert2343 avatar Mar 19 '22 18:03 robert2343

Ah, that message appears when the browser prevents audio playback until an initial user interaction occurs. Clicking that link is supposed to provide that initial interaction and allows audio playback to proceed. Apparently it's not doing that for some reason. Needs investigation

ken107 avatar Mar 19 '22 20:03 ken107

🖕🏻🖕🏻🖕🏻🤣❤️

On Sat, Mar 19, 2022, 2:52 PM robert2343 @.***> wrote:

I am running Librewolf (fork of Firefox), which I installed from Flatpak on Linux Mint (which is why it is in a sandbox), and I am trying to try to Google Translate English option, and every time I try to read anything aloud, it says "click here to start", and when I click there, that message goes away, then reappears after about a second. I get no sound. It works on normal Firefox, installed by default on my distribution.

— Reply to this email directly, view it on GitHub https://github.com/ken107/read-aloud/issues/261, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASVKAZZEZFFANIT5QNUJTHDVAYO57ANCNFSM5REL4LJA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Juelzz avatar Mar 19 '22 20:03 Juelzz

I don't have the Real Aloud extension in librewolf working, either.

DmitriyPekar avatar Mar 22 '22 20:03 DmitriyPekar

Hi, just following up to see if anything has been done about this yet. No pressure if it hasn't. Just wondering. Thanks

robert2343 avatar Apr 13 '22 22:04 robert2343

Sorry, I haven't had time to look into this. We've run into this with the various forks of the main browsers. As far as I can tell, it is not something we can workaround.

Basically when we call audio.play() it returns an error saying the user hasn't interacted with the page yet, and prevents the audio from being played. So we display a link in the error message ("click here to start"), that's supposed to furnish that initial user gesture. It worked for Brave (I think that's where we initially implemented it), but apparently not for many of the Firefox forks.

ken107 avatar Apr 15 '22 09:04 ken107