lidlanca

fixed ```html {@html html}{''} ```

bug related to fix made for https://github.com/vuejs/vue/issues/6566 https://github.com/vuejs/vue-next/blob/870f2a7ba35245fd8c008d2ff666ea130a7e4704/packages/runtime-dom/src/modules/events.ts#L118-L128 The issue is, that for browsers where the event uses the hi-res timestamp The child window time resets/start from 0, when the...

same story for elements moved to an iframe.

another workaround ```html // Skip timestamp check workaround. // Code must be called before vue runtime is imported/evaluated. /* const ffMatch = navigator.userAgent.match(/firefox\/(\d+)/i); skipTimestampCheck2 = !!(ffMatch && Number(ffMatch[1]) { let...

this is a bug 🐛 the compiler does not detect `果物` as an identifier of the v-for scope ```html {{ 果物 }} ``` and caches the handler ```js onClick: _cache[0]...

https://github.com/HcySunYang/rfcs/blob/keepalive-cache-management-and-match-rules/active-rfcs/0000-keepalive-cache-management-and-match-rules.md [#4339 ](https://github.com/vuejs/core/pull/4339)

its been open for more than a year, I don't know what blocks it.

double triggering the effect, might be something that can be fixed, but perhaps with a different approach. Returning the ref when you pass it through `reactive()` might not be expected...

@hubvue it will probably be best to avoid passing a ref directly to `reactive(ref())` I don't see a good reason for this. do you have a practical use case, where...

the types seem to be inferred correctly ( unless I miss understand your point)  there is no `reactive` type per say, as it is basically a transparent proxy with...