via https://github.com/atom/less-cache/pull/17
Less 3 has a way smaller dependency tree and reduces our `npm audit` from `4 vulnerabilities` to 4. (and the remaining 4 are just regex issues, which should never have counted as vulnerabilities in the first place.)
From Electron 20 onwards, preload scripts are sandboxed by default and no longer have access to a full Node.js environment. Practically, this means that you have a polyfilled require function that only has access to a limited set of APIs.
https://www.electronjs.org/docs/latest/tutorial/tutorial-preload
Related discussion: https://github.com/ianstormtaylor/slate/issues/5108
This block undoes the addition of div.onbeforeinput = () => {}. This is very, very
gross, but Slate uses the presence of this handler (Added in Chrome 105) to activate a
new version of it's event handling, which doesn't quite work properly in our old version
of Slate: https://github.com/ianstormtaylor/slate/issues/5108#issuecomment-1297591129
Since this was added to Chrome in v105, we can be fairly confident nothing else needs
it to exist, or will similarly fall back to document.addEventListener('beforeInput')
One day, we will update Slate to the latest version, but 0.50.x is effectively a rewrite
and we have /lots/ of custom plugins that need to be re-built and re-tested.
* snap: Remove various unneeeded plugs
Remove various permissions that the snap required and that are not
actually used. In particular now all the file and settings access is handled
by XDG portals, so there's no need to grant direct file access.
Also this is not a media app or network management software, so no
need to add screen inhibitors or network observation.
* snap: Do not add libnss3
That's already provided by GNOME so no need to duplicate it.
* Update snapcraft.yaml
Put back password-manager-service, home for now
---------
Co-authored-by: Ben Gotow <bengotow@gmail.com>
Was able to determine that this was the problem by bisecting our Electron upgrade and identifying which chrome version bump broke it, and then googling for slate + chrome version.
It looks like this entire concept of webkit-user-modify is deprecated, so I have no idea why this matters, but it looks like they changed the default to read-write-plaintext and it broke Slate for everyone.
https://github.com/ianstormtaylor/slate/issues/5110
* feats: add script to improve localization
* fix: the script used to generate the translations didn't take certain concatenations into account.
Previously :
Many features are unavailable in plain-text mode. To create a single
Now :
Many features are unavailable in plain-text mode. To create a single plain-text draft, hold Alt or Option while clicking Compose or Reply.
-
Previously :
These features were %@ of the messages you sentin this time period, so these numbers do not reflect all of your activity. To enableread receipts and link tracking on emails you send, click the %@ or link tracking %@ icons in the composer.
Now :
These features were %@ of the messages you sent in this time period, so these numbers do not reflect all of your activity. To enable read receipts and link tracking on emails you send, click the %@ or link tracking %@ icons in the composer.
-
Previously :
To make changes to contacts in this account, you'll need to re-authorize Mailspring to access your data.\n\n
Now :
To make changes to contacts in this account, you'll need to re-authorize Mailspring to access your data.\n\nIn Mailspring's main window, go to Preferences > Accounts, select this account, and click \"Re-authenticate\". You'll be prompted to give Mailspring additional permission to update and delete your contacts.
...
* chore: improving the french and format-localizations.js executed
* feats: add templates to localizations
* fix(localization): define default template to english
* chore(localization): added explanations on how to use script files
---------
Co-authored-by: Ben Gotow <ben@foundry376.com>
The commit fixes a bug where the dateLikeString was not being formatted
correctly if it only contained 3 or 4 digits. The fix adds a check for
this case and formats the string accordingly.
Additionally, the commit addresses an issue where the time was not being
set correctly if the "gotTime" variable was false. The fix adds a check
for each iteration of the loop to ensure that the time is only set if
the corresponding "gotTime" value is false.
