Franz Josef Kaiser

_imho_ This should be determined by the implementation, not the application itself.

@MarcelHekkert This is stated in the first paragraph in the first sentence of the readme.

Follow up: The tags [need to be fixed](http://stackoverflow.com/a/21741848/376483) as their _original_ date prevents the correct order of tags. **Warning:** Tedious job ahead…

As it turns out, Google limits cert validity to 398 (397) days, effective with 2020-09-01. [Announcement in full length here](https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/certificate_lifetimes.md). This results in `mkcert` being effectively broken for Chrome/ Chromium...

@FiloSottile Could you please take a look at the issue and the provided PR? Thanks in advance!

The version is correct and `v1.4.3` as reported above. But you have been right regarding the date. I double and tribble checked and noticed at some point that even if...

@filippobuletto yes, I am sure about that. But please don't get me wrong here: I assume that this does not happen because of mkcert. Below you can find a cert...

The only "solution" (which is none) I could come up with so far, is to import the store directly in the component: ```js import store from "./store" const myVue =...

Additional note: The same problem also applies to events. Emitting events outside the component is possible. Listening to these events from inside a cell rendered component not.

I just opened the example [and switched to version `3.0.97+`](https://codesandbox.io/s/dfgsdfssdf-forked-cxb8w). The sorting still is off: * 1 * 11.1 * 2.1 * 3 * 4 * 6 * 7 Seems...