GitLab

Otherwise we might mess up a script trying to reparent it elsewhere.
This fixes Netflix...

BUG: 432043

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"

GIT_SILENT

GIT_SILENT

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"

A data URL isn't very meaningful to the user, so show the referrer URL
as download source. Also store it in origin URL attribute since a data URL
contains no origin and also isn't very useful as it just contains the data
of the file we've just downloaded.

While at it, optimize `descriptionDirty` to check whether it actually changed
before emitting a description change.

Like we do it these days

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"

They are typically added to the DOM (a video the user can't see isn't very useful),
but in case the website just renders the video offscreen into a texture, our brief
DOM dance will still cause trouble.

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"

It's a little awkward having a link "additional permissions"
that does nothing when the permission was already granted.

Instead, check for the permission and show a "You have already
granted this permission." messsage, for which we conveniently
already have a string from the request page.

microsoft-edge.desktop will be the desktop file name used by the
stable version once it's released.

Effectively, the Task Manager method would be used mainly anyway.

Leverages its heuristic for finding desktop files and lets us support
pretty much any browser without the need to hardcode a mapping.

The browser still sends us its environment as a fallback. It is also
used so we at least have a baseline of "this is a Firefox derivate" or
"a Chromium browser" since some parts of the host react differently
based on the environment.

Score results that contain the term in its unbroken consecutive form
slightly higher than ones that are a mere subsequence.

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"

It seems to read Chrome's config, too, for compatibility but let's use what the
documentation [1] says.

[1] https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/native-messaging?tabs=linux

I just noticed Chrome errors out on opening most of the external links we
have on the options page (e.g. the "KDE Connect" link).

Just open all of them in a new tab, which we probably want explicitly anyway.

the .pot file has lines starting and ending in quotes
we used strip(\") to get rid of them.

If a string ends in ", it will appear as "" in the file, and both
characters get stripped.

Instead chop the first and last characters

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"