Bug 395521 - Tweetdeck shows playback even though there is nothing playing
Summary: Tweetdeck shows playback even though there is nothing playing
Status: RESOLVED FIXED
Alias: None
Product: plasma-browser-integration
Classification: Plasma
Component: Firefox (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
: 397161 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-06-17 10:36 UTC by nostalgia.ninja
Modified: 2018-09-21 21:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Media Player plugin after video has been played. (62.91 KB, image/png)
2018-06-17 10:36 UTC, nostalgia.ninja
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nostalgia.ninja 2018-06-17 10:36:50 UTC
Created attachment 113387 [details]
Media Player plugin after video has been played.

When TweetDeck is opened, (tweetdeck.twitter.com), the timeline begins to stream.  Once playback is done through a video, the plasma integration plugin activates, but does not deactivate when the video is stopped by closing the media player window.
Comment 1 Kai Uwe Broulik 2018-08-01 12:08:04 UTC
Git commit 09c729554ea1b5bea52f01b0d9a86f76f24e500d by Kai Uwe Broulik.
Committed on 01/08/2018 at 12:07.
Pushed by broulik into branch 'master'.

Also monitor DOM node being removed for player gone

We currently only monitor the tab being closed or navigating away from the page but when a video overlay opens using JavaScript,
we didn't notice that it was gone when the overlay was closed

Differential Revision: https://phabricator.kde.org/D14207

M  +29   -5    extension/content-script.js

https://commits.kde.org/plasma-browser-integration/09c729554ea1b5bea52f01b0d9a86f76f24e500d
Comment 2 Patrick Silva 2018-08-05 14:10:22 UTC
*** Bug 397161 has been marked as a duplicate of this bug. ***
Comment 3 Niklas 2018-09-21 21:34:21 UTC
I am still experiencing this issue, nothing changed with the update to v1.3 of the extension.