owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
vuejs | core | 1,330,207,275 | 6,921 | edison1105 | duplicate of #6435 | 2022-11-29T07:39:45 | 2022-11-29T07:39:45 | {} | MEMBER |
vuejs | core | 1,331,020,822 | 7,240 | LinusBorg | ~~https://github.com/vuejs/docs/issues/2112 brought up some path worth exploring, maybe, so I'll reopen this for the moment.~~
Not really an option after. all.
FWIW, you can hack around the limitation with things like:
```js
class X {
#a = 'secret'
#b = 'secret'
getPropA = () => this.#a
constructo... | 2022-11-29T17:29:30 | 2022-11-29T17:41:23 | {} | MEMBER |
vuejs | core | 1,333,122,407 | 7,252 | edison1105 | > Infinite recursion is prevented. Any frame that attempts to assign as its SRC a URL used by any of its ancestors is treated as if it has no SRC URL at all (basically a blank frame). This doesn't prevent all malicious documents, but it eliminates a troublesome class of them.
see https://www.w3.org/TR/WD-frames-9703... | 2022-12-01T03:44:34 | 2022-12-01T03:44:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,333,831,368 | 6,859 | obj63mc | Been watching this issue and wanted to note that we are also seeing this for other html elements such as video too.
For images - the other props being stripped are fetchpriority for proper priority hints setting.
For video - the muted attribute is stripped. | 2022-12-01T14:14:14 | 2022-12-01T14:14:14 | {
"+1": 1
} | NONE |
vuejs | core | 1,335,390,133 | 7,258 | Sight-wcg | > Yeah, I tried to use Firefox. It works in Chrome and Edge though.
>
> Could Vuex, Vue Router and Bootstrap be added too?
>
> > Failed to resolve module specifier "vuex".
> > Tip: add an "import-map.json" file to specify import paths for dependencies.
>
> > Failed to resolve module specifier "vue-router".
>... | 2022-12-02T15:10:51 | 2022-12-02T15:11:06 | {} | NONE |
vuejs | core | 1,326,681,797 | 7,207 | LinusBorg | > Is there a best practice for how to implement something like a tooltip?
With a component, usually. Not a custom directive.
> Is there somewhere suitable to document in Vue.js docs that this should not be done
Likely somewhere at the end of this introduction section, the info-box already goes a bit in the rig... | 2022-11-24T16:55:54 | 2022-11-24T17:01:58 | {} | MEMBER |
vuejs | core | 1,327,891,849 | 7,185 | prashantpalikhe | One advantage I could think of is while using the playground on an iPad. That would be pretty nice to have the devtools there too. | 2022-11-25T21:24:32 | 2022-11-25T21:24:32 | {
"+1": 1
} | NONE |
vuejs | core | 1,328,267,349 | 7,223 | bomzj | @LinusBorg could you provide a link to this open RFC? | 2022-11-27T15:14:09 | 2022-11-27T15:14:09 | {} | NONE |
vuejs | core | 1,329,326,302 | 6,479 | msimpson | @LinusBorg
Understood. I will continue to wrap my state refs in composable customRef-based filters/validators within setup, instead. | 2022-11-28T15:46:35 | 2022-11-28T15:46:35 | {} | NONE |
vuejs | core | 1,334,899,459 | 5,657 | william-iq397 | > related #5650
>
> the error message is not same in chrome and firefox:
>
> chrome: 
>
> firefox: ... | 2022-12-02T08:24:38 | 2022-12-02T08:24:38 | {} | NONE |
vuejs | core | 1,335,238,709 | 7,264 | LinusBorg | Closing as reproduction is missing. | 2022-12-02T13:30:40 | 2022-12-02T13:30:40 | {} | MEMBER |
vuejs | core | 1,335,257,986 | 7,199 | g1eny0ung | @sxzz Can this PR be merged? | 2022-12-02T13:50:12 | 2022-12-02T13:50:12 | {} | CONTRIBUTOR |
vuejs | core | 1,324,886,293 | 7,197 | LinusBorg | ~~https://vuejs.org/guide/typescript/composition-api.html#syntax-limitations~~
~~Also see #4294~~ | 2022-11-23T11:07:54 | 2022-11-23T11:11:26 | {} | MEMBER |
vuejs | core | 1,311,848,989 | 7,103 | LinusBorg | 😮 thanks | 2022-11-11T15:40:04 | 2022-11-23T22:25:38 | {} | MEMBER |
vuejs | core | 1,327,964,989 | 7,216 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | eff6f03a68d2da862bedb380171bfc38626a8b25 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-26T02:38:39 | 2022-11-26T02:38:39 | {} | NONE |
vuejs | core | 1,329,315,140 | 7,175 | yooouuri | @edison1105
Removed the innerHTML key.
Build Vue locally, used locally build `@vue/server-renderer`.
Sadly doesn't work.
![image](https://user-images.githubusercontent.com/12934957/204318702-c... | 2022-11-28T15:39:45 | 2022-11-28T15:39:45 | {} | NONE |
vuejs | core | 1,330,809,093 | 7,240 | LinusBorg | ES6 proxies simply don't support private fields which is a huge PITA., but consequently this is unfortunately a wontfix, or rather "can't fix".
FWIW, we always recommend to use POJOs for reactive state. We need to be more explicit about this specific hard limitation in the docs, though. | 2022-11-29T15:16:11 | 2022-11-29T15:16:11 | {} | MEMBER |
vuejs | core | 1,331,487,513 | 7,244 | justinwinslow | Also, fwiw, this seems to be the case for both examples if the whole project is set to MODE 2 or 3 and same at just the component level. | 2022-11-30T00:21:22 | 2022-11-30T00:21:22 | {} | NONE |
vuejs | core | 1,333,709,509 | 7,258 | jacekkarczmarczyk | @edison1105 it has: https://unpkg.com/@vue/devtools-api/lib/esm/index.js | 2022-12-01T12:41:28 | 2022-12-01T12:41:28 | {} | CONTRIBUTOR |
vuejs | core | 1,325,228,108 | 6,273 | i404788 | @LinusBorg I'm running into this issue and your comment is somewhat confusing, could you clarify how the following point works:
```
let ganttBars = shallowRef<GanttEntry[]>([]);
ganttBars.value = [...ganttBars.value]; // Does trigger component->watch(data)
triggerRef(ganttBars) // Does not trigger component->watch(... | 2022-11-23T15:11:08 | 2022-11-23T15:14:08 | {} | NONE |
vuejs | core | 1,326,222,371 | 7,201 | edison1105 | It's easy to solve. see [demo](https://sfc.vuejs.org/#eNp1UWFrhDAM/SulDLzB2X4XNxjsHwz2Zd0Hp7k7D21LE91A/O+L1cptYyCYvKQvL3mTfPJejQPIQpZYh9bTo7Hw5V0g0cCpGjoSk7FC1K73zoIlLGIuxEvtPKRECB+cx+ItwwXO3o8JD2AbCIf7vXGBaAhW0KVFdYedI1TbrEPEIsV96p/XIP5mpjXUA11csws5Az1XVN2MqJ1F14Hq3PmQbeVsJ0zjwwC31MbyZ2yp9ztwQtD7riLgTIiyaccYcBi3F0WU+m... | 2022-11-24T10:03:21 | 2022-11-24T10:04:52 | {} | MEMBER |
vuejs | core | 1,327,663,799 | 7,213 | Asylian21 | Agree, this is the thing that is awesome on svelte. Just remove the template tag. | 2022-11-25T16:09:33 | 2022-11-25T16:09:33 | {
"+1": 2
} | NONE |
vuejs | core | 1,328,250,722 | 7,223 | LinusBorg | This issue should be a comment on the still open RFC. | 2022-11-27T13:47:00 | 2022-11-27T13:47:00 | {} | MEMBER |
vuejs | core | 1,331,377,588 | 7,243 | LinusBorg | we can't debug minified code. Please provide a runnable reproduction that contains clear code. | 2022-11-29T22:02:08 | 2022-11-29T22:02:08 | {} | MEMBER |
vuejs | core | 1,333,655,872 | 7,258 | edison1105 | [pinia.esm-browser](https://unpkg.com/browse/pinia@2.0.27/dist/pinia.esm-browser.js) dependency on [@vue/devtools-api](https://unpkg.com/browse/@vue/devtools-api@6.4.5/lib/esm/) which seems not have a esm-browser version.
| 2022-12-01T11:58:32 | 2022-12-01T11:58:32 | {} | MEMBER |
vuejs | core | 1,334,872,252 | 7,218 | Justineo | Shall we align the design with [petite-vue](https://github.com/vuejs/petite-vue) (which uses `v-scope` and an object carrying the local variables)? | 2022-12-02T07:52:51 | 2022-12-02T07:52:51 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,334,888,775 | 7,214 | edison1105 | the root cause is
```javascript
// Comp is not an async component.
const { Comp } = useRenderSlowComponent()
```
see [workaround](https://sfc.vuejs.org/#eNp9VMGOmzAQ/RWLC0QikPZISaRVLz1WTdVL3QMlk8AKbMs2SVeR/73jMVDYbdY54DHPw5v3ZnKPnpTKrgNERVSaWrfKMgN2UAcu2l5JbdmdaTinDXPsrGXPYgTHi5eDgW8gTqCPnbx9lngsQNgZneUzIHs2eJG... | 2022-12-02T08:11:49 | 2022-12-02T08:29:56 | {} | MEMBER |
vuejs | core | 1,324,785,476 | 7,196 | Asylian21 | I see, thanks for help. This should be better explained in docs. | 2022-11-23T09:44:00 | 2022-11-23T09:44:00 | {} | NONE |
vuejs | core | 1,324,894,502 | 7,197 | dotSILENT | This happens when TS is not used and this method of defining props with custom classes is even referenced in Vue's guide to prop validation: https://vuejs.org/guide/components/props.html#runtime-type-checks | 2022-11-23T11:14:41 | 2022-11-23T11:15:31 | {} | NONE |
vuejs | core | 1,324,978,910 | 7,175 | yooouuri | @zhangzhonghe I forgot something to mention...
Im trying to render a json-ld script.
Updated playground: https://sfc.vuejs.org/#eNp9jz9PwzAQxb+KdUtANPZuBSTExgADqxc3vbSu4j86X4OqKN+dM2KoQGK7e+/0e+9WeC5FLxcECwNjLLNnfHJJqeElx5ITJlY21EcHXR0pFO4cKL4WFMWXMofRc8jJzIeHc81JzKU/cZzFfv14f9OVKaRjmK53q5pytqrbe+rUdi+XRoIGc5MKOw... | 2022-11-23T12:21:04 | 2022-11-23T12:23:06 | {} | NONE |
vuejs | core | 1,326,293,865 | 6,984 | bauer00 | I've also tested that and I can reproduce this behaviour. I've added a log to both the `module_test_plugin.ts` and `test_plugin.ts`. Adding `vue` or the `@test/module` to resolve.dedupe didn't help.
When I looked at the location where the logs were executed I saw this behaviour:
![grafik](https://user-images.github... | 2022-11-24T11:04:15 | 2022-11-24T11:04:15 | {} | NONE |
vuejs | core | 1,328,267,550 | 7,223 | LinusBorg | https://github.com/vuejs/rfcs/pull/420 | 2022-11-27T15:15:21 | 2022-11-27T15:15:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,328,328,381 | 6,479 | LinusBorg | I'll close this as i don't consider it a bug. The chosen pattern/custom ref implementation is simply not compatible with a component controlled with v-model.
Child Components don't re-render when props don't change - that's a fundamental principle in y Vue's renderer. | 2022-11-27T20:02:54 | 2022-11-27T20:02:54 | {} | MEMBER |
vuejs | core | 1,330,859,986 | 7,241 | LinusBorg | All of this is expected. you are not controlling the checkbox properly. when the checkbox is changed - in the UI - to "checked", you don't reflect that in a state change: `state.checked` stays `false` - so Vue has no reason to re-render (as no reactive state changed), and thus the checkbox in the UI will remain check... | 2022-11-29T15:51:17 | 2022-11-29T15:53:20 | {} | MEMBER |
vuejs | core | 1,316,273,746 | 7,108 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | f8fcfb18e43ac9f26e8fc01a44f9de5e08e01fce |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-16T03:34:18 | 2022-12-02T01:11:11 | {} | NONE |
vuejs | core | 1,334,753,399 | 1,324 | douglasg14b | If this is intended, does that mean we cannot use generic fucntions with refs? Or is there some way we are supposed to be doing this?
For instance (contrived example)
```ts
function useThing<T>(value: number) {
const valueRef = ref(value);
function setValue(val: T) {
valueRef.value = val;
... | 2022-12-02T04:33:21 | 2022-12-02T05:00:48 | {
"+1": 3,
"rocket": 1
} | NONE |
vuejs | core | 1,334,926,614 | 7,218 | edison1105 | > Shall we align the design with [petite-vue](https://github.com/vuejs/petite-vue) (which uses `v-scope` and an object carrying the local variables)?
Excellent advice. I will try it later. | 2022-12-02T08:52:46 | 2022-12-02T08:52:46 | {} | MEMBER |
vuejs | core | 1,335,875,765 | 2,349 | funkyvisions | Something like this can work too (works well when you have multiple instances, unlike the one above)
```
beforeUpdate(el) {
if (el.isConnected && !el.isActive) {
el.isActive = true
activated(el)
}
if (!el.isConnected && el.isActive) {
el.isActi... | 2022-12-02T21:49:17 | 2022-12-02T21:50:46 | {} | NONE |
vuejs | core | 1,418,203,315 | 5,525 | johanmolen | @liulinboyi any special configs options used there? | 2023-02-05T18:05:10 | 2023-02-05T18:05:10 | {} | NONE |
vuejs | core | 1,418,492,722 | 5,678 | flynn-eye | > I have the same problem
>
> ------- error ------- main.2ff0ecbab0eb3f2c70e2.js:634 Uncaught TypeError: Cannot read properties of null (reading 'setupContext') at sr (runtime-core.esm-bundler.js?0d3f:7489:14) at setup (index.vue?3169:39:7) at callWithErrorHandling (runtime-core.esm-bundler.js?85e2:155:24) at setupS... | 2023-02-06T04:19:52 | 2023-02-06T04:19:52 | {} | NONE |
vuejs | core | 1,420,630,445 | 7,649 | lehni | Follow up: ~It does indeed solve this problem~ (**Update**: that's sadly not the case, see below), but note that the docs only mention `async` dependencies, not this particular use-case. It's definitely not something one would naturally expect to solve this problem:
https://stackblitz.com/edit/vue-3-transition-with-... | 2023-02-07T11:35:21 | 2023-02-07T12:19:49 | {} | CONTRIBUTOR |
vuejs | core | 1,425,010,522 | 7,679 | baiwusanyu-c | #5688 | 2023-02-10T00:21:13 | 2023-02-10T00:21:28 | {} | MEMBER |
vuejs | core | 1,418,418,456 | 7,654 | LittleSound | LGTM | 2023-02-06T02:37:57 | 2023-02-06T02:37:57 | {} | MEMBER |
vuejs | core | 1,419,315,454 | 7,652 | zh-lx | > 给个标准连接呢，我查mdn没有查到，如果真的不符合原始行为，我觉得还是有必要做加强
There is the description about `CustomEvent.detail` in MDN: [https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/detail#value](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/detail#value)：
![image](https://user-images.githubusercontent.com/7305962... | 2023-02-06T15:56:28 | 2023-02-06T16:13:25 | {} | CONTRIBUTOR |
vuejs | core | 1,419,835,405 | 2,669 | madebyfabian | Is this still relevant? | 2023-02-06T22:01:57 | 2023-02-06T22:01:57 | {
"eyes": 1
} | NONE |
vuejs | core | 1,422,952,930 | 7,649 | AlexVagrant | Hi guy, I know how to solve this bug.
It's a `Transition` bug, when we use `v-if` in `Transition` and the `v-if` result is false, Vue will insert a comment node to replace origin component, it is a placeholder node.
`Transition` get all children from slots, but the `<!--v-if-->` comment can't get from slots, this... | 2023-02-08T17:04:56 | 2023-02-08T17:04:56 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,424,179,812 | 6,220 | UnluckyNinja | @mrleblanc101
You should start a new issue as it's actually a different topic. This is a closed issue, and you will probably not get an answer.
Also, it seems to be a coding problem rather than an issue related to Vue. And you might misunderstand what the warning says. There are better places for that.
But still, h... | 2023-02-09T13:17:26 | 2023-02-09T13:17:26 | {} | NONE |
vuejs | core | 1,425,027,011 | 6,220 | mrleblanc101 | @UnluckyNinja Thanks for your time, I found this one while doing research and it felt pretty close to what I needed to solve my issue (a global inject), also opened a new issue because I might have found a bug related to the alternative someone suggested me (use inject inside the props default factory function) https:/... | 2023-02-10T00:49:45 | 2023-02-10T00:49:45 | {} | NONE |
vuejs | core | 1,425,225,598 | 5,938 | mrleblanc101 | I think this is still an issue with Boolean, it maybe a regression ? See #7677 | 2023-02-10T05:54:45 | 2023-02-10T05:54:45 | {} | NONE |
vuejs | core | 1,414,717,146 | 7,638 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 404ba92918512c0c2142e912bbd6cc95e7a229af |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2023-02-03T02:40:34 | 2023-02-03T02:40:34 | {} | NONE |
vuejs | core | 1,414,717,379 | 7,638 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 404ba92918512c0c2142e912bbd6cc95e7a229af |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2023-02-03T02:40:41 | 2023-02-03T02:40:41 | {} | NONE |
vuejs | core | 1,418,550,316 | 7,655 | mrleblanc101 | This might be a Nuxt bug 🤔 | 2023-02-06T05:45:33 | 2023-02-06T05:45:33 | {} | NONE |
vuejs | core | 1,421,858,155 | 7,658 | starcsb | > > it can also be a string type when used in html
>
> Certain browsers may support that, but it's not in the spec:
>
> > The attributes, if specified, must have values that are valid non-negative integers.
>
> https://html.spec.whatwg.org/multipage/embedded-content-other.html#attr-dim-height
>
> Vue also s... | 2023-02-08T02:08:47 | 2023-02-08T02:08:47 | {} | NONE |
vuejs | core | 1,421,898,056 | 7,658 | Justineo | @LinusBorg
> in what way does this break in certain cases in CSR?
https://github.com/vuejs/core/blob/6c6fe2c0cd89ce513503b1f85e0ddb696fd81e54/packages/compiler-dom/src/transforms/stringifyStatic.ts#L83-L86
There's currently a `createStaticVNode` optimization which stringifies vnodes into HTML so it works simi... | 2023-02-08T02:41:19 | 2023-02-08T02:42:24 | {} | MEMBER |
vuejs | core | 1,425,196,156 | 7,655 | mrleblanc101 | This is actually an issue because I was using `npm link` to test my package and my package was on Vue 3.2.46 while my app was in 3.2.47 | 2023-02-10T05:32:45 | 2023-02-10T05:32:45 | {
"+1": 1
} | NONE |
vuejs | core | 1,416,820,586 | 7,161 | sxzz | https://github.com/vuejs/core/commit/53e3533b75adc32f979adde34bde3b581e48084b
P.S Wait https://github.com/vuejs/repl/pull/58 for Vue repl | 2023-02-04T18:32:27 | 2023-02-04T18:33:39 | {} | MEMBER |
vuejs | core | 1,418,541,545 | 7,655 | mrleblanc101 | I dug into the Vue-core test and I don't see what my issue is.
https://github.com/vuejs/core/blob/main/packages/dts-test/appUse.test-d.ts | 2023-02-06T05:30:39 | 2023-02-06T05:30:39 | {} | NONE |
vuejs | core | 1,418,635,040 | 7,656 | Justineo | You cannot use a `'</script>'` string literal inside the `<script>` block in an HTML page. This is how HTML parsers expected to work and Vue's SFC syntax is HTML-compliant which means the restriction also applies to it.
You can work this around either as suggested by the [HTML spec](https://html.spec.whatwg.org/mult... | 2023-02-06T07:32:53 | 2023-02-06T07:32:53 | {} | MEMBER |
vuejs | core | 1,420,186,732 | 7,665 | yogeshgalav | The following functionality is already available but not clearly defined,
With element approach it can be clearly defined and scoped.
1. If the component is of element="input" type,
then v-model should automatically work on component,
Without defining emit "input".
2. If the component is of element="button" type... | 2023-02-07T04:31:29 | 2023-02-07T04:31:29 | {} | NONE |
vuejs | core | 1,420,272,894 | 7,665 | LinusBorg | Please use the RFC process for proposals of complex changes such as this: https://github.com/vuejs/rfcs
FWIW: I'm not in convinced. | 2023-02-07T06:41:38 | 2023-02-07T06:41:38 | {} | MEMBER |
vuejs | core | 1,420,329,876 | 7,666 | LinusBorg | However generally, i'd ask you to peovide a reproduction that does not import a whole component library unless that is required to repeoduce the issue (which should be stated as such) | 2023-02-07T07:44:34 | 2023-02-07T07:44:34 | {} | MEMBER |
vuejs | core | 1,420,577,578 | 7,659 | zh-lx | > Different how? Is there an issue for that problem with SSR?
Yes, you can enable SSR in this demo:
https://sfc.vuejs.org/#__SSR__eNp9UEFOwzAQ/MriSy91nLYUQRQq8Q9fnHSTGGrHrJ22UpW/s2kqQCD1ZM/OeHY8F/EWQnYcUBSijDXZkCBiGsJOe+tCTwkuQNjACA31DhYsXWivfalmNesYJHThYBIyAii71c66tlR8XvGDlHCy+9QVsMrBRvA9OXMA4/fQoW2ZWD+G88SY6sZJOb... | 2023-02-07T10:54:57 | 2023-02-07T10:57:18 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,425,574,655 | 7,590 | pi0 | Update: I have updated the tests. Also made this change completely opt-in via a private API. When `globalThis.__vue_ctx__` is set, vue reuses the context over package-scoped context. | 2023-02-10T10:22:16 | 2023-02-10T10:22:16 | {} | NONE |
vuejs | core | 1,416,788,784 | 7,585 | AlexVipond | Close but not quite—`defineComponent` accepts a setup function that can return a render function. It returns a full component with its own lifecycle.
`defineFunctionalComponent` should accept the render function itself, not a setup function, and it should be a no-op (it should just return the render function, which re... | 2023-02-04T16:01:33 | 2023-02-04T16:02:23 | {
"+1": 2
} | NONE |
vuejs | core | 1,420,340,317 | 7,666 | lixiaofa | > However generally, i'd ask you to peovide a reproduction that does not import a whole component library unless that is required to repeoduce the issue (which should be stated as such)
The solution given by discussions is to manually change the packaged code, which I think is not so good
This iss should be opened
... | 2023-02-07T07:53:40 | 2023-02-07T07:54:21 | {} | NONE |
vuejs | core | 1,420,344,168 | 7,666 | LinusBorg | I will do that, once you or someone else provides me with a *minimal* reproduction that we can evaluate efficiently.
Your project repository is no such minimal reproduction, and in the vite issue, no one cared to provide one, either. | 2023-02-07T07:57:43 | 2023-02-07T07:57:43 | {} | MEMBER |
vuejs | core | 1,421,814,648 | 7,542 | edison1105 | It is inconsistent with vue2. so I feel this should be a bug. | 2023-02-08T01:41:51 | 2023-02-08T01:41:51 | {} | MEMBER |
vuejs | core | 1,425,465,608 | 7,684 | baiwusanyu-c | I think this isn't a bug too.
`{{ text = ['1,2,3,4,5'] }}` is compiled by the compiler into code `text.value = ['1,2,3,4,5']`, and rendered run when. And `v-show` just controls the display property. `text.value = ['1,2,3,4,5']` will still execute, which I think is expected | 2023-02-10T09:11:38 | 2023-02-10T09:12:43 | {} | MEMBER |
vuejs | core | 1,418,177,512 | 7,652 | LinusBorg | I'm confused. You say additional event content should not be exposed as an array. But your "proposed API" example shows just that: the arguments being exposed as an array.
So which is it? And if now an array, how should it work? | 2023-02-05T17:17:20 | 2023-02-05T17:17:48 | {} | MEMBER |
vuejs | core | 1,418,393,960 | 7,652 | zh-lx | > I'm confused. You say additional event content should not be exposed as an array. But your "proposed API" example shows just that: the arguments being exposed as an array.
>
> So which is it? And if now an array, how should it work?
There are two examples in my "proposed API". My mean is when the number of addi... | 2023-02-06T02:12:38 | 2023-02-06T02:12:38 | {} | CONTRIBUTOR |
vuejs | core | 1,420,275,814 | 7,659 | LinusBorg | Thanks for this PR, but the current behavior is just what the browser does according to the spec. We should not do any special handling here, the developer should provide the value in the correct type. | 2023-02-07T06:44:51 | 2023-02-07T06:44:51 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,420,739,873 | 7,658 | LinusBorg | > it can also be a string type when used in html
Certain browsers may support that, but it's not in the spec:
> The attributes, if specified, must have values that are valid non-negative integers.
https://html.spec.whatwg.org/multipage/embedded-content-other.html#attr-dim-height
Vue also supports strings,... | 2023-02-07T13:04:35 | 2023-02-07T13:04:35 | {} | MEMBER |
vuejs | core | 1,420,680,476 | 7,649 | lehni | Ok, click the `Step` button repeatedly at high frequency in the new version of the reduced test-case that include `<Suspense>` here, and you'll get the same errors. This definitely doesn't fix this bug:
https://stackblitz.com/edit/vue-3-transition-with-root-level-v-if-and-suspsense
<img width="950" alt="image" sr... | 2023-02-07T12:17:03 | 2023-02-07T14:02:48 | {} | CONTRIBUTOR |
vuejs | core | 1,423,732,311 | 6,220 | mrleblanc101 | I'm creating a Vue plugin.
It provide a component, the component has some sane default props value.
I want to let the use override the props value in the `app.use(component, options)`.
If I do this:
```js
const options = inject<PluginOptions>(PLUGIN_KEY);
const props = withDefaults(defineProps<Props>(), {
... | 2023-02-09T07:08:06 | 2023-02-09T07:08:06 | {} | NONE |
vuejs | core | 1,425,585,736 | 7,684 | Justineo | You are modifying data while rendering the component so this is expected behavior. Currently you are not supposed to declare variable inside templates. | 2023-02-10T10:30:48 | 2023-02-10T10:30:48 | {} | MEMBER |
vuejs | core | 1,414,596,102 | 7,188 | edison1105 | > Hello! Can you please tell me if there is a chance that this fix will be released soon?
Maybe in 3.3 | 2023-02-03T01:38:07 | 2023-02-03T01:38:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,418,025,779 | 5,525 | liulinboyi | > @liulinboyi
>
> This is a simplified example: [stackblitz.com/edit/vitejs-vite-bqescg?file=src/App.vue](https://stackblitz.com/edit/vitejs-vite-bqescg?file=src/App.vue)
>
> Works fine in dev but not once it is builded.
I have download [stackblitz.com/edit/vitejs-vite-bqescg?file=src/App.vue](https://stackbli... | 2023-02-05T15:13:57 | 2023-02-05T15:13:57 | {} | MEMBER |
vuejs | core | 1,420,274,958 | 7,658 | LinusBorg | I'm with edison here. The developer should provide a number as that's what's expected by the HTML spec. We should not start adding code to special handle such cases. | 2023-02-07T06:43:38 | 2023-02-07T06:43:38 | {} | MEMBER |
vuejs | core | 1,420,327,265 | 7,666 | LinusBorg | I dont speak chinese. I took the referral to the vite issue and your thanks as an indictor that this has been or at least needs to be resolved in Vite. And as This seems to about the code produced by Vite's bundle process, and not code from vue core, It makes sense to me to solve it there.
If thats not the case, I c... | 2023-02-07T07:43:28 | 2023-02-07T07:53:24 | {} | MEMBER |
vuejs | core | 1,420,347,895 | 7,666 | lixiaofa | > Link to minimal reproduction
> However generally, i'd ask you to peovide a reproduction that does not import a whole component library unless that is required to repeoduce the issue (which should be stated as such)
Link to minimal reproduction：
https://github.com/lixiaofa/vant-sku-next
@LinusBorg | 2023-02-07T08:01:37 | 2023-02-07T08:01:37 | {} | NONE |
vuejs | core | 1,420,369,101 | 7,666 | LinusBorg | A project with that many dependencies and files in the src folder is not, by any sense of the word, "minimal".
```json
{
"dependencies": {
"@vant/touch-emulator": "^1.4.0",
"@vant/use": "^1.4.3",
"axios": "^1.2.1",
"echarts": "^5.4.1",
"lodash-es": "^4.17.21",
"nprogress": "^0.2.0",
... | 2023-02-07T08:18:32 | 2023-02-07T08:18:32 | {} | MEMBER |
vuejs | core | 1,425,476,639 | 7,590 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8a0083ce847974de05dea17afd1c72af4fda7490 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-02-10T09:19:56 | 2023-02-10T10:20:58 | {} | NONE |
vuejs | core | 1,420,639,165 | 7,649 | lehni | Oh, and when using this feature, you end up with such messages in the console:
`<Suspense> is an experimental feature and its API will likely change.` | 2023-02-07T11:43:10 | 2023-02-07T11:43:10 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,420,615,033 | 7,659 | zh-lx | > Thanks for this PR, but the current behavior is just what the browser does according to the spec. We should not do any special handling here, the developer should provide the value in the correct type.
Although the description of `width` of `<img>` on MDN must be a integer, it can also be a string type when used i... | 2023-02-07T11:22:29 | 2023-02-07T12:34:00 | {} | CONTRIBUTOR |
vuejs | core | 1,403,066,869 | 7,086 | wucdbm | @yyx990803 Managed to narrow this down to instances where a `<template>` has a v-if on it, in `runtime-dom.esm-bundler.js` `nodeOps.insert` `parent` is `NULL`
The reason for using a <template v-if></template> is to avoid polluting the DOM with redundant DIVs
It seems that it can recover successfully from DIVs wit... | 2023-01-25T04:05:48 | 2023-02-07T23:11:20 | {} | NONE |
vuejs | core | 1,422,798,490 | 7,669 | MajedMuhammad | @LinusBorg that works! Thanks!
But actually this makes it not consistent as a built-in component or a globally-registered component should be rendered by pass only the component name, not the component raw! | 2023-02-08T15:32:16 | 2023-02-08T15:32:16 | {} | NONE |
vuejs | core | 1,423,758,400 | 5,220 | Autumn-one | > For your specific use case, you can just switch from declaring an event to a prop:
>
> ```js
> props: ['onClose'],
> // instead of:
> emits: ['close'],
> ```
>
> Event Listeners are passed as props with an `on` prefix, so these two declarations both represent an event. Meaning, if you have an `onClose` prop... | 2023-02-09T07:37:13 | 2023-02-09T07:37:13 | {} | NONE |
vuejs | core | 1,424,037,610 | 7,649 | AlexVagrant | > @AlexVagrant great find! Are you working on a PR to fix this?
Yes, I will fix this bug soon, please give me a little time. | 2023-02-09T11:27:44 | 2023-02-09T11:27:44 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,425,416,840 | 7,402 | edison1105 | @baiwusanyu-c
I believe the root cause is the same. | 2023-02-10T08:36:51 | 2023-02-10T08:36:51 | {} | MEMBER |
vuejs | core | 1,418,060,250 | 6,435 | wvffle | @edison1105 Can we get any ETA for this issue? | 2023-02-05T15:41:51 | 2023-02-05T15:41:51 | {
"+1": 4
} | NONE |
vuejs | core | 1,419,190,543 | 7,652 | baiwusanyu-c | 给个标准连接呢，我查mdn没有查到，如果真的不符合原始行为，我觉得还是有必要做加强 | 2023-02-06T14:40:03 | 2023-02-06T14:40:03 | {} | MEMBER |
vuejs | core | 1,420,213,694 | 7,666 | lixiaofa | > see [vitejs/vite#7592](https://github.com/vitejs/vite/discussions/7592)
Thank you ！！！ | 2023-02-07T05:14:25 | 2023-02-07T05:14:25 | {} | NONE |
vuejs | core | 1,420,270,464 | 7,652 | LinusBorg | It's hard to change now, as all users of a Vue web component now already use it like this. So it's a breaking change. | 2023-02-07T06:38:08 | 2023-02-07T06:38:08 | {} | MEMBER |
vuejs | core | 1,420,272,108 | 7,658 | edison1105 | Duplicate of https://github.com/vuejs/core/issues/2801
the height or width must be an integer without a unit.
see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img?retiredLocale=de#attr-height | 2023-02-07T06:40:32 | 2023-02-07T06:41:01 | {} | MEMBER |
vuejs | core | 1,420,322,529 | 7,666 | lixiaofa | > see [vitejs/vite#7592](https://github.com/vitejs/vite/discussions/7592)
Is there an official solution？
@LinusBorg | 2023-02-07T07:40:41 | 2023-02-07T07:40:41 | {} | NONE |
vuejs | core | 1,420,502,108 | 7,659 | Justineo | Current behavior for CSR and SSR is different. And under certain optimization in CSR the behavior is also different. I think this is a bug and should be fixed. | 2023-02-07T10:01:34 | 2023-02-07T10:01:34 | {} | MEMBER |
vuejs | core | 1,420,626,148 | 7,649 | lehni | Thank you @AlexVagrant for pointing this out, but I am not sure it's save to use `<Supsense>`? From the docs:
> `<Suspense>` is an experimental feature. It is not guaranteed to reach stable status and the API may change before it does.
https://vuejs.org/guide/built-ins/suspense.html
And if this is indeed the s... | 2023-02-07T11:31:32 | 2023-02-07T11:32:18 | {} | CONTRIBUTOR |
vuejs | core | 1,414,397,134 | 7,635 | LinusBorg | you are missing a pair of brackets to actually *call* the function. | 2023-02-02T21:28:21 | 2023-02-02T21:28:21 | {} | MEMBER |
vuejs | core | 1,414,629,377 | 6,164 | pohnean | This is useful for me as well, I've created a PR for this. | 2023-02-03T01:59:07 | 2023-02-03T01:59:07 | {} | NONE |
vuejs | core | 1,414,697,643 | 7,629 | edison1105 | Type verification is performed only in the development environment and not in the production environment. So the production environment type is changed to null.
However, there is still a problem with this demo. When switching to DEV, it returns an error. This is something we need to solve.(**It will be fixed in the `r... | 2023-02-03T02:28:35 | 2023-02-03T03:16:42 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.