You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well , this is a bug , that i have no doubt .
Setting The Subtitles in maximum size in firefox 52 i get the subtitles with acceptable
size to be read .
But when i change to firefox 60 , the subtitles also setting up in their max size in streama stays very small , hardly to read .
Is there a way to fix this .
Actually i think that the maximum size should be much bigger than firefox 52 actually shows .
Anyway , here are the print screens .
Firefox 52 , streama configured with subtitles in Max size
Firefox 60 , streama configured with subtitles in Max size (Impossible to read).
The text was updated successfully, but these errors were encountered:
yup , this is why i have 2 firefox versions installed , the 52 esr and the latest , when i want to watch some movie using streama i will use 52 version , and when i want to surf the web i will use the latest .
I dont like Chrome , however this is probably not a streama bug but a firefox incompatibility , but i am not sure .
Well , this is a bug , that i have no doubt .
Setting The Subtitles in maximum size in firefox 52 i get the subtitles with acceptable
size to be read .
But when i change to firefox 60 , the subtitles also setting up in their max size in streama stays very small , hardly to read .
Is there a way to fix this .
Actually i think that the maximum size should be much bigger than firefox 52 actually shows .
Anyway , here are the print screens .
Firefox 52 , streama configured with subtitles in Max size

Firefox 60 , streama configured with subtitles in Max size (Impossible to read).

The text was updated successfully, but these errors were encountered: