| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* New translations en-US.json (Romanian)
* New translations en-US.json (Turkish)
* New translations en-US.json (Portuguese)
* New translations en-US.json (Russian)
* New translations en-US.json (Slovak)
* New translations en-US.json (Slovenian)
* New translations en-US.json (Serbian (Cyrillic))
* New translations en-US.json (Swedish)
* New translations en-US.json (Ukrainian)
* New translations en-US.json (Norwegian)
* New translations en-US.json (Chinese Simplified)
* New translations en-US.json (Chinese Traditional)
* New translations en-US.json (Vietnamese)
* New translations en-US.json (Portuguese, Brazilian)
* New translations en-US.json (Indonesian)
* New translations en-US.json (Croatian)
* New translations en-US.json (Flemish)
* New translations en-US.json (Polish)
* New translations en-US.json (Dutch)
* New translations en-US.json (French)
* New translations en-US.json (German)
* New translations en-US.json (Spanish)
* New translations en-US.json (Afrikaans)
* New translations en-US.json (Arabic)
* New translations en-US.json (Belarusian)
* New translations en-US.json (Catalan)
* New translations en-US.json (Czech)
* New translations en-US.json (Danish)
* New translations en-US.json (Greek)
* New translations en-US.json (Korean)
* New translations en-US.json (Finnish)
* New translations en-US.json (Irish)
* New translations en-US.json (Hebrew)
* New translations en-US.json (Hungarian)
* New translations en-US.json (Italian)
* New translations en-US.json (Japanese)
* New translations en-US.json (Georgian)
* New translations en-US.json (Bosnian)
|
|
|
|
| |
context menu actions (#1494)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Expose Chrome version to todos webview (fix #1211)
The TickTick todo service fails to load if the Chrome version number
does not appear in the User-Agent string. However, login to Google Tasks
is prevented by the same.
We adopt the "chromeless" User-Agent logic from the service webview,
which selectively exposes the Chrome version everywhere except the
Google login screen. The common logic was moved into the
userAgent-helpers module.
* Refactor user agent switching
* "Chromeless" user agent switching is extracted into a separate model
* Both the service and the todos webview uses the same model
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* docs: update README.md [skip ci]
* docs: update .all-contributorsrc [skip ci]
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
|
| |
|
|
|
|
| |
neeeded attrs
|
| |
|
|
|
|
|
| |
Also pulls in the 5.6.0-beta.5 changelog for GitHub releases
Co-authored-by: Vijay Raghavan Aravamudhan <vraravam@users.noreply.github.com>
|
| |
|
|
|
|
|
| |
Makes the service and workspace count badges more readable in the
settings dialog.
|
|
|
|
|
| |
Previously, the shadow was only applied to the sidebar of the dialog.
Also fixes the rendering artifacts near the close button.
|
|
|
|
|
|
|
|
|
|
|
|
| |
SCSS functions apply absolute change to the color lightness values, but
the 'color' npm package does relative changes. This lead to inconsistent
behavior between the default and custom accent colors.
See also https://github.com/Qix-/color/issues/53#issuecomment-656590710
We use relative adjustment for buttons. For the service switcher in
light mode, we use relative adjustment instead, because absolute
adjustment made the buttons too hard to see (#235).
|
|
|
|
|
|
|
|
|
| |
Bumps [ws](https://github.com/websockets/ws) from 6.2.1 to 7.4.6.
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](https://github.com/websockets/ws/compare/6.2.1...7.4.6)
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
| |
Extracted from 240c3a72363e7388779c9ed3c6467ec63bb64d94 according to
https://github.com/getferdi/ferdi/pull/1456#discussion_r641182688 and
https://github.com/getferdi/ferdi/pull/1456#discussion_r641183662
|
|
|
|
|
|
|
|
|
|
|
| |
* Extract screenshare into a separate file
Extracted from 240c3a72363e7388779c9ed3c6467ec63bb64d94 according to
https://github.com/getferdi/ferdi/pull/1456#discussion_r641194876
* Cosmetic screenshare changes and cancellation
* Makes the screen/window selector more readable
* Adds a Cancel button to close the selector
|
|
|
|
| |
Extracted from 357b23b69c119e3d10926613ca31588d5c7285fc according to
https://github.com/getferdi/ferdi/pull/1456#discussion_r641185050
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Restore ELECTRON_IS_DEV environment variable
As part of migrating to @electron/remote from electron.remote, 296ce5ce6
removed the electron-is-dev package and with it the support of selecting
dev/production mode with the ELECTRON_IS_DEV environmental variable.
This commit restores support for this variable. Because even the newest
version of the electron-is-dev package breaks in renderer processes, we
instead query the environment ourselves.
* Add support for NODE_ENV variable
Also support NODE_ENV for specifying dev mode in addition to the
ELECTRON_IS_DEV variable. This variable is used by e.g., the packaging
in Arch Linux to trigger production mode with an explicit electron
command line invocation:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ferdi-git&id=61dc59e5eb19a2c9e8f9edaf0a63aaae72990a0b#n109
* Refactor environmental variable handling
|
|
|
|
| |
system deps (node, etc).
|
|
|
| |
Related to https://github.com/getferdi/ferdi/issues/475#issuecomment-849416883
|
| |
|
| |
|
|
|
| |
* Locked new version of 'recipes' submodule with corresponding changes.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Bump dbus-next to 0.9.2
Older dbus-next seems to have problems with building with Electron 13
ABI. Also upgrades nan (a transitive dependency of dbus-next) to 2.14.2.
* Explcitly specify Electron ABI 89
electron-rebuild seems to have problems with finding the correct ABI for
Electron 13, despite node-abi being updated to the latest version and
containing an entry for Electron 13 in abi-registry.json. This is
probably caused by Electron 13 still being marked as a future target in
abi-registry.json.
This commit pins the ABI version to 89 for Electron 13 and should be
reverted once node-abi marks Electron 13 as released.
|
| |
|
|
|
|
| |
subnodule.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
builds [skip ci]
Dont wait for publishing artifact - in case that step fails. This is
because, this failure causes all subsequent builds to also fail stating
artifact file already exists while publishing (since the build version
number change gets lost).
|
| |
|
|
|
|
| |
- so that appveyor doesn't skip as well.
|
| |
|
|
|
|
|
|
| |
'electron-builder'.
For more info: https://github.com/electron-userland/electron-builder/issues/3179
|
| |
|
|
|
|
| |
service. (#1439)
|
| |
|
| |
|
|
|
|
| |
[skip ci]
|
|
|
|
| |
subnodule.
|
| |
|
|
|
|
| |
blank screen.
|