Edit by @tofumatt: to clarify, this restriction only applies to Safari and its Intelligent Tracking Prevention. Safari sites will be affected by this change, but apps using their own wrapped web views (eg webview apps, Ionic apps, etc.) will not be affected.

Apple announced changes to the script writeable storages on iOS 13.4 and Safari 13.1:
https://webkit.org/blog/10218/full-third

I'm probably missing something obvious, but neither the website nor this repo has any documentation.

Is this a markdown editor I can embed in my "classic" rendered (html rendered by server) websites?

Do I have to build my own version?
Can I use npm to import it?
Is there any documentation?

I couldn't load and build the project using the latest qt creator and the wiki guide for building, i think it's out dated, please update and add more details for beginners who want to contribute.

When rotating between landscape/portrait, you can lose your open document and position. I have encountered this issue on an iPhone XS Max running iOS 12.3.1.

Steps to recreate:

• Search for something.
• View an article.
• Rotate into landscape mode (on my iPhone XS Max, this shows the search view and the document view side-by-side)
• Rotate back to portrait

Expected behavior: Show

The documentation doesn't mention a way to change the name of the generated file.

It does mention gulp, but I am using Angular 4's angular-cli to generate my assets and then run sw-precache separately to generate the service worker.

the packages.json file consists of this command:
"sw": "sw-precache --config=sw-precache-config.js --verbose"

And the sw-precache-config.js file has the

Need help providing more samples and better flow documentation of the DBCore interface and all its methods and related interfaces. For a skilled developer, it is possible to lab with DBCore even based on the minimal docs we have now, by looking at existing middlewares and create a custom middleware.

There is a skelleton of docs around the DBCore interface right now that is not very easy to foll

As caught by @OliverJAsh:
Hey! The fixed background is causing the whole page to be repainted on scroll, FYI

Are you aware of any different behavior when a PWA (using offline-plugin) is added to the home screen using "Add to Home Screen" on Chrome/Android or Safari/iOS?

I'm having problems with the app getting stuck using the cached version when it was installed and never updating.
I even have offline-plugin responseStrategy set to network-first but it seems to always use the cached version after add

In many older tutorials, we use things like var and .then() that we forbid in our actual codebase. It would be more readable if the docs used a more modern syntax, especially around Promises. Not only is await easier to read, but our use of .then() in docs may mislead a reader into thinking that they must do the same.

There is a user with a dick pic as their icon. Many people have blocked them, as have I.

I recently clicked through to their profile page to remember if I had blocked them and although their posts are hidden, their user icon is still shown.

Can we use CSS to blur the user icons of blocked and ignored users?

filter: blur(8px);
-webkit-filter: blur(8px);

(Those icons might al

Meta info

• Is this a bug or suggestion?: Bug
• Version (click on help icon in footer): 4.0.3
• Contex: Chrome Extension

The "Read the documentation" link in the help window generates a file-not-found error:

Your file was not found
It may have been moved or deleted.
ERR_FILE_NOT_FOUND
— chrome-extension://lkfkkhfhhdkiemehlpkgjeojomhpccn

General informations

• system/distribution (with version): Debian Buster
• offlineimap version (offlineimap -V): offlineimap v7.2.3
• Python version: v2.7.16
• server name or domain: Amazon WorkMail
• CLI options: nothing special

Configuration file offlineimaprc

[Repository WorkMail-Remote]
type = IMAP
remotehost = imap.mail.eu-west-1.awsapps.com
remoteuser = REDAC

I see that new yjs is coming with Snapshots, will they be able to restore the whole document to a specific state based on StateSet and DeleteSet ?

What I did in the earlier version was essentialy packing the document into a syncStep2 message to specific state and then feeding this message to a new document.

function backDocToState(doc, state) {
  const { ss, ds } = state
  const needS

The issue I'm experiencing is pretty annoying.
I'm trying to optimize my first byte, by turning off compression, and gziping everything by webpack with CompressionPlugin. The issue is that it doesn't compress service-worker.js produced by sw-precache-webpack-plugin.

I understand the reason why: service-worker.js should cache all chunks produced by webpack after CompressionPlugin compress

I really like the new design of the webpage. A few suggestions/comments:

• The initial page is a bit empty and doesn't give much insight into how zettlr looks / works. For example, compare it to the landing page of https://code.visualstudio.com/. I would propose to add a screenshot to left as for the visual studio page, or move everything up a bit and add a screenshot that overflows to the second

As PWA add to home screen workflow is different on each platform/browsers, we could add a button on the interface to trigger the installation. It will standardize add to home screen workflow for all browsers.

See official doc
for more informations

This project is using sw-precache instead of the latest @angular/service-worker and ng-pwa-tools.

At Google I/O last week, they announced that https://github.com/GoogleChrome/workbox would be the preferred option over sw-precache going forward.

However, Angular seems to be creating a better integrated SW and PWA story using the tools mentioned above. That said, it would be interesting to

Version

v2.10.2

Reproduction link

https://github.com/nuxt-community/modules/blob/master/packages/browserconfig/index.js

Steps to reproduce

path.resolve(this.options.srcDir, 'static', browserconfigFileName) and `content: '/' + browserconfigFi

I'm submitting a...

[x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[x] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/f

if you modify the swDest option to generate the serviceworker in other path, this not affect the path to generate the development service-worker.

I need to see the code to fix this, but would be nice to have this in the documentation.
this is the fix to generate serviceworker in development in the right path.

  dontAutoRegisterSw: true,
  devSwSrc: {
    from: './public/sw-dev.js'

From https://github.com/npm/validate-npm-package-name:

package name should not start with . or _

Try to replace tarballs to _tarballs from URL to avoiding conflict.