https://bugs.kde.org/show_bug.cgi?id=395214
--- Comment #8 from Johannes Falke ---
I can confirm both Emby and Home Assistant now work when not manually enabling
the new experimental setting on 1.1. Great work!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395214
David Edmundson changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=395214
--- Comment #6 from Bernhard ---
(In reply to David Edmundson from comment #5)
> Short term fix patches in review. Should be fixed soon.
>
> Thanks again for detailed description
Thank you for caring enough about the quality of the plasma desktop to
https://bugs.kde.org/show_bug.cgi?id=395214
--- Comment #5 from David Edmundson ---
Short term fix patches in review. Should be fixed soon.
Thanks again for detailed description
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395214
--- Comment #4 from David Edmundson ---
Bug only exhibits itself when using the Chrome media sessions API shim.
Which isn't too surprising as that code is doing something horrific to
communicate between the two JS contexts instead of just watching the
https://bugs.kde.org/show_bug.cgi?id=395214
David Edmundson changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=395214
David Edmundson changed:
What|Removed |Added
CC||johannesfa...@googlemail.co
https://bugs.kde.org/show_bug.cgi?id=395214
--- Comment #1 from Bernhard ---
Created attachment 113203
--> https://bugs.kde.org/attachment.cgi?id=113203=edit
Home-Assistant loading correctly
I set up a instance of homeassistant for testing at
https://homeassistant.bmicraft.net/
(Found out the