Jump to content

Plasma/Browser Integration: Difference between revisions

From KDE Community Wiki
Eiglow (talk | contribs)
Grammar and punctuation
Tosky (talk | contribs)
How to help: IRC -> libera
Line 48: Line 48:
If you find an issue, please check the [https://bugs.kde.org/buglist.cgi?list_id=1517340&product=plasma-browser-integration&resolution=--- list of open bugs], and then [https://bugs.kde.org/enter_bug.cgi?product=plasma-browser-integration file a bug report].
If you find an issue, please check the [https://bugs.kde.org/buglist.cgi?list_id=1517340&product=plasma-browser-integration&resolution=--- list of open bugs], and then [https://bugs.kde.org/enter_bug.cgi?product=plasma-browser-integration file a bug report].


For help and suggestions, you'll find us in #plasma on Freenode IRC.
For help and suggestions, you'll find us in #plasma on Libera Chat IRC.


You can browse the source code on KDE's GitLab instance: https://invent.kde.org/plasma/plasma-browser-integration  
You can browse the source code on KDE's GitLab instance: https://invent.kde.org/plasma/plasma-browser-integration  

Revision as of 20:01, 18 June 2021

This project aims to provide better integration of web browsers with the Plasma desktop.

What is it?

Plasma Browser Integration is a system for common browsers to closer fit into the Plasma shell. This includes:

  • Media Controls
    • Lets you control video and audio players in websites using the Media Controller plasmoid, media keys on your keyboard, and even remotely from your phone
  • Send links via KDE Connect
    • Adds a context menu entry to links, enabling you to send them to your phone and other paired devices
  • Show and control downloads from Plasma’s notification area
    • Optionally store address a file was downloaded from in its metadata
  • Let websites prompt for sharing contents to other applications
  • Find browser tabs in the Run Command (Alt-Space) window
    • Make sure the "Browser Tabs" module is enabled in Plasma Search (KRunner) settings

How to install

The extension consists of two parts:

  • The native host: An application that runs on your computer that the browser extension talks to:
    • It should be available as a package from your distribution.
    • If building from the source into a custom prefix, you will want to build with -DCOPY_MESSAGING_HOST_FILE_HOME to install the files firefox/chrome need
    • See Chrome documentation and Firefox documentation for where the native host and its accompanying configuration file must be placed in.

Privacy

Generally, everything is handled on your PC between the browser and your desktop.

Note, however:

  • When using Tabs Runner, the extension will query the browser for website favicons of all open pages. They are open already anyway, so this normally won't result in any additional network activity.
  • When using Enhanced Media Controls, the extension will announce a website-provided album cover image URL, which may be downloaded and displayed outside the browser, such as by the desktop shell.
  • A website might be able to detect that you are using this extension by querying for specific objects added to the website's environment.

KDE's Privacy Policy applies.

How to help

If you find an issue, please check the list of open bugs, and then file a bug report.

For help and suggestions, you'll find us in #plasma on Libera Chat IRC.

You can browse the source code on KDE's GitLab instance: https://invent.kde.org/plasma/plasma-browser-integration