GitLab

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Should the player be added with a short sound but then change its duration,
we would never have tracked it as pending player.

Websites typically set all their callbacks (play, pause, nexttrack, previoustrack, etc) in one go,
which would have us send them over from the content script to the extension and to the host, signalling
individual MPRIS property changes. Optimize this by batching subsequent calls.

Furthermore, check if playbackState and metadata actually changed before sending them over.
There's no point in sending the data over to the host which will then find they haven't changed.

The object behind the "mediaSessionsClassName" is turned into a "class" (not ES6 Class for Firefox ESR
compat) and an instance is created. This allows using "this" from within its handlers, cleaning
up the code somewhat.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Got broken when I meddled with the menus...
Just call the callback for each device to ensure behavior stays in sync here.

(Ideally we'd have some Port class where a module could register a callback
to get notified of when the host connects/disconnects :)

At this point we end up sending pretty much everyting, there's no real point in filtering anymore.

They are mostly meant to detect when a player is dynamically added/removed by AJAX when e.g.
an overlay opens.
I don't think it's necessary to monitor the page being constructed, potentially slowing it down.
Especially since in DOMContentLoaded we will register all players anyway.

They're not http or https URLs. Add a dedicated handler with appropriate "Call on device" label and icon.
The URL pattern doesn't look like any of the listed examples, but tel://*/* would refuse on grounds that "tel"
isn't a recognized schema but just doing "tel:*" works on both Firefox and Chrome.

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

GIT_SILENT

GIT_SILENT

They advertise supporting Chrome extensions

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

Test Plan: Builds

Reviewers: broulik

Reviewed By: broulik

Subscribers: plasma-devel

Tags: #plasma

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

Media Sessions artwork takes precedence, if set.

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