Andrew

@nolimits4web the workaround that worked for me was to update navigation after a delay in nextTick like so: ``` mounted() { this.$nextTick(() => { setTimeout(() => this.slider.navigation.update(), 0) } }...

Ok, so in order to have IE11 support we will have to stick to using utilities such as `.text-primary-75` instead of `.text-primary text-opacity-75` right?

I can live with that 😄

Any updates on this PR?

@thgreasi `localForage-memoryStorageDriver` looks interesting but documentation doesn't provide a full example of using it. Maybe you could provide an example of how a situation of not having any local storage...

I was able to reproduce the issue by manually disabling Cookies in the global Chrome settings https://take.ms/nXAWX @thgreasi is there a way to detect whether storage options are available in...

@Chris1234567899 could you share your setup regarding `localforage-driver-memory` ? Do you import it with a static import or it can be dynamically imported only for users that doesn't allow cookies?

@salidean what do you think about such strategy? ``` import * as localForage from 'localforage' import * as memoryDriver from 'localforage-driver-memory' localForage.defineDriver(memoryDriver) localForage.setDriver([localForage.LOCALSTORAGE, localForage.INDEXEDDB, localForage.WEBSQL, memoryDriver._driver]) ``` I want to...

That's why he said it's not ideal solution

I'm using 0.22.9 version but the issue is still present