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 | 808,185,565 | 3,491 | edison1105 | Duplicate of #2736 ? | 2021-03-26T12:42:23 | 2021-03-26T12:44:12 | {} | MEMBER |
vuejs | core | 808,721,817 | 3,493 | HcySunYang | As an afterword, it seems that this PR(https://github.com/vuejs/vue-next/pull/3334) will encounter the same situation, since https://github.com/vuejs/vue-next/pull/3334 has been marked as a plan for 3.1, maybe we can introduce these changes together in 3.1 ? | 2021-03-27T12:00:55 | 2021-03-27T12:00:55 | {} | MEMBER |
vuejs | core | 808,748,495 | 3,334 | yyx990803 | I think this is worth it - we probably will have to introduce a "semi breaking change" in 3.1 where **pre-compiled components using version >=3.1.0 will not work with runtime <3.1.0**.
Btw it needs to be rebased now | 2021-03-27T15:20:09 | 2021-03-27T15:20:09 | {} | MEMBER |
vuejs | core | 809,120,895 | 3,503 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.34 KB (0%) |
| runtime-dom.global.prod.js | 27.42 KB (0%) |
| size-check.global.prod.js | 16.58 KB (0%) | | 2021-03-29T06:54:33 | 2021-03-29T06:54:33 | {} | NONE |
vuejs | core | 805,133,709 | 3,469 | Livijn | I created a Vue 2 sandbox, and this DOES NOT happen in vue 2: https://codesandbox.io/s/focused-glade-qj11z?file=/src/main.js | 2021-03-23T18:30:58 | 2021-03-23T18:30:58 | {} | NONE |
vuejs | core | 806,280,559 | 3,478 | edison1105 | this is intened
https://github.com/vuejs/vue-next/blob/master/packages/reactivity/src/reactive.ts#L73-L84
```javascript
// only unwrap nested ref
type UnwrapNestedRefs<T> = T extends Ref ? T : UnwrapRef<T>
/**
* Creates a reactive copy of the original object.
*
* The reactive conversion is "deep"—it affe... | 2021-03-25T00:58:14 | 2021-03-25T00:58:14 | {} | MEMBER |
vuejs | core | 808,491,721 | 2,654 | yyx990803 | See better fix in 60d777d2 | 2021-03-26T20:30:05 | 2021-03-26T20:30:05 | {} | MEMBER |
vuejs | core | 808,754,278 | 2,602 | kospl | @JasperTey your case looks behaving this way because of this internal compiler bug: https://github.com/vuejs/vue-next/issues/3392
| 2021-03-27T16:02:46 | 2021-03-27T16:02:46 | {} | NONE |
vuejs | core | 809,096,168 | 3,258 | HcySunYang | @nandi95 this needs to be rebased now | 2021-03-29T06:06:58 | 2021-03-29T06:06:58 | {} | MEMBER |
vuejs | core | 809,142,935 | 81 | HcySunYang | Hi, thanks for this PR, but it is stale so close it now | 2021-03-29T07:31:06 | 2021-03-29T07:31:06 | {} | MEMBER |
vuejs | core | 809,517,788 | 3,514 | edison1105 | > Already fixed in [69b4727](https://github.com/vuejs/vue-next/commit/69b4727204256795d37a29930be33ab4f864af38) - the original variable declaration walk is too loose.
WoW, You solved it when I was submitting the code. | 2021-03-29T16:19:13 | 2021-03-29T16:19:13 | {} | MEMBER |
vuejs | core | 806,007,665 | 2,827 | thexeos | Even with moderately sized code-base this suddenly popped up in a few places for us after trying vue/next. Webpack hot-reload took the initial blame, as it seemed the file itself was not being properly loaded (parent component being loaded in place of the child component with the same file-name).
For us, the use cas... | 2021-03-24T17:14:55 | 2021-03-24T17:14:55 | {} | NONE |
vuejs | core | 748,504,020 | 2,851 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 41.29 KB (+0.07% 🔺) |
| runtime-dom.global.prod.js | 27.39 KB (+0.16% 🔺) |
| size-check.global.prod.js | 16.57 KB (+0.13% 🔺) | | 2020-12-19T17:48:50 | 2021-03-26T19:37:09 | {} | NONE |
vuejs | core | 808,718,022 | 3,493 | HcySunYang | > That's not really what we want to do unless absolutely necessary in terms of bug fixing
This is a necessary refactoring for slot scope id, see https://github.com/vuejs/vue-next/pull/3374, yes, this is a breaking change for library authors.
I just realized that the build resources of `vue-mapbox-ts` contain out... | 2021-03-27T11:31:58 | 2021-03-27T11:31:58 | {} | MEMBER |
vuejs | core | 808,720,261 | 3,493 | HcySunYang | I agree, but this is actually a problem that must occur during dev or build process. Users should be easy to detect and it does not seem to bring hidden risks to users. | 2021-03-27T11:46:58 | 2021-03-27T11:46:58 | {} | MEMBER |
vuejs | core | 809,121,918 | 3,506 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.34 KB (0%) |
| runtime-dom.global.prod.js | 27.42 KB (0%) |
| size-check.global.prod.js | 16.58 KB (0%) | | 2021-03-29T06:56:25 | 2021-03-29T06:56:25 | {} | NONE |
vuejs | core | 805,115,579 | 2,064 | tbtalbottjr | Just wanted to confirm that using the "resolve" entry that @skirtles-code provided allows me to do a 'yarn link' to a library I am trying to help convert over to Vue 3. Prior to that, I had to point to a github repository and do a push to get the library to work correctly. I was having the same issue that a second vers... | 2021-03-23T18:04:34 | 2021-03-23T18:05:55 | {} | NONE |
vuejs | core | 808,850,884 | 3,334 | HcySunYang | Should be fine now | 2021-03-28T05:38:57 | 2021-03-28T05:38:57 | {} | MEMBER |
vuejs | core | 809,246,376 | 3,497 | holtwick | Please bump this up, it is a showstopper for i18n and `<teleport>` use, see https://github.com/intlify/vue-i18n-next/issues/412 | 2021-03-29T09:56:40 | 2021-03-29T09:56:40 | {
"+1": 9
} | NONE |
vuejs | core | 809,195,247 | 3,509 | HcySunYang | See the latest commit | 2021-03-29T08:47:40 | 2021-03-29T08:47:40 | {} | MEMBER |
vuejs | core | 809,502,222 | 3,490 | yaquawa | I just want to use the `isNativeTag` option so I can determine which tag is a component or not. | 2021-03-29T16:00:07 | 2021-03-29T16:00:07 | {} | NONE |
vuejs | core | 805,615,286 | 3,308 | BeneStem | Is this version already released? | 2021-03-24T08:45:24 | 2021-03-24T08:45:24 | {} | NONE |
vuejs | core | 805,790,203 | 3,475 | Justineo | Though #3477 may fix that `null` values were rendered as `"null"`, the difference between Vue 2 and 3 still exists and is intentional.
And there's still an issue to be investigated that `<option :value="null">` is rendered as `<option value="">`, which does not comply with our latest coercion behavior. | 2021-03-24T12:44:52 | 2021-03-24T12:44:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 806,348,126 | 2,827 | HcySunYang | @luwuer Can you draft an RFC? If you don't have time, I can do this instead | 2021-03-25T04:07:13 | 2021-03-25T04:07:13 | {} | MEMBER |
vuejs | core | 806,532,012 | 3,486 | LinusBorg | This repository is for Vue 3, not Vite's Vue integration. Please open an issue there.
as a hint: You likely didn't configure the JSX options in Vite correctly, and so the compiler inserts the default JSX pragma, which imports Reacts | 2021-03-25T10:21:44 | 2021-03-25T10:22:31 | {} | MEMBER |
vuejs | core | 806,533,134 | 3,478 | LinusBorg | duplicate of #1135 | 2021-03-25T10:23:27 | 2021-03-25T10:23:27 | {
"-1": 1
} | MEMBER |
vuejs | core | 808,415,142 | 3,461 | yyx990803 | It's cheaper to not have to maintain a stack by storing the prev instance before setting a new instance (like we are already doing in `withCtx`). See 8c3c14a0 | 2021-03-26T18:01:34 | 2021-03-26T18:01:34 | {} | MEMBER |
vuejs | core | 808,865,849 | 3,493 | relief-melone | I can confirm that with 3.0.9 everything is working again as expected. Thanks alot | 2021-03-28T08:35:12 | 2021-03-28T08:35:12 | {
"+1": 2
} | NONE |
vuejs | core | 809,699,116 | 3,502 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-29T20:41:28 | 2021-03-29T20:41:28 | {} | CONTRIBUTOR |
vuejs | core | 809,699,126 | 3,506 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-29T20:41:29 | 2021-03-29T20:41:29 | {} | CONTRIBUTOR |
vuejs | core | 805,563,645 | 3,472 | HcySunYang | Closed because of duplication | 2021-03-24T07:15:53 | 2021-03-24T07:15:53 | {} | MEMBER |
vuejs | core | 807,960,782 | 3,487 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.16 KB (0%) |
| runtime-dom.global.prod.js | 27.29 KB (0%) |
| size-check.global.prod.js | 16.51 KB (0%) | | 2021-03-26T06:02:03 | 2021-03-26T06:02:03 | {} | NONE |
vuejs | core | 807,961,112 | 3,488 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.16 KB (0%) |
| runtime-dom.global.prod.js | 27.29 KB (0%) |
| size-check.global.prod.js | 16.51 KB (0%) | | 2021-03-26T06:02:51 | 2021-03-26T06:02:51 | {} | NONE |
vuejs | core | 808,716,430 | 3,493 | LinusBorg | @HcySunYang Then this is a breaking change introduced in a patch release.
That's not really what we want to do unless absolutely necessary in terms of bug fixing, I would say.
We should discuss this in the team, re-evaluate the real impact of this on lib maintainers and come up with a strategy to handle this si... | 2021-03-27T11:22:43 | 2021-03-27T11:24:40 | {} | MEMBER |
vuejs | core | 808,718,634 | 3,493 | LinusBorg | Still, if it's breaking a ton of libs, we should consider rolling this back, communicating the change with the community and give them time to prepare.
Because at the end, it's not only affecting lib authors, it would break many apps that *use* a lib that was compiled with a compiler version `<3.0.8`, with no clear ... | 2021-03-27T11:35:43 | 2021-03-27T11:35:43 | {
"+1": 2
} | MEMBER |
vuejs | core | 808,721,918 | 3,493 | LinusBorg | > I agree, but this is actually a problem that must occur during dev or build process. Users should be easy to detect and it does not seem to bring hidden risks to users.
Yes, people upgrading to 3.0.8 will likely find this bug during build, and can then roll back to 3.0.7.
Still, this is problematic. `3.0.8` bri... | 2021-03-27T12:01:35 | 2021-03-27T12:07:56 | {} | MEMBER |
vuejs | core | 809,000,955 | 3,001 | edison1105 | > I don't think it is a separate problem, it's just another manifestation of the same bug in the decoder.
>
> I believe the fix I proposed would work for both.
Oh, I was so sorry for misunderstood your point. | 2021-03-29T01:05:23 | 2021-03-29T01:05:23 | {} | MEMBER |
vuejs | core | 809,363,632 | 3,500 | gkandemi | > This is expected, if you want to inject the reactive version, you need to wrap the `commentList` with another object, see https://codepen.io/hcysunyang/pen/yLgJGJQ
Really thanks :) I guess missed the some point at somewhere :) | 2021-03-29T13:09:13 | 2021-03-29T13:09:13 | {} | NONE |
vuejs | core | 809,539,013 | 3,389 | b12f | Yes https://github.com/vitejs/vite/issues/2446#issuecomment-796974065 | 2021-03-29T16:50:31 | 2021-03-29T16:50:31 | {} | NONE |
vuejs | core | 743,117,267 | 2,790 | qq397023775 | I think this is a bug, if you replace [patchKeyedChildren](https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/renderer.ts#L1579) with `patchUnkeyedChildren`, then everything will work fine.
Check this link, the click event will be bound to `div(foo)`: https://codesandbox.io/s/throbbing-snowfla... | 2020-12-11T10:38:05 | 2020-12-11T10:41:33 | {
"+1": 2
} | NONE |
vuejs | core | 744,187,288 | 2,790 | qq397023775 | > Hook mounted is trigger after patch.
Completely wrong, the patch here refers to the update triggered after changing the reactive data. the `mounted` is always before the `updated`. | 2020-12-14T05:52:27 | 2020-12-14T05:52:27 | {} | NONE |
vuejs | core | 744,225,740 | 2,812 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-14T07:12:54 | 2020-12-14T07:12:54 | {} | NONE |
vuejs | core | 744,739,769 | 2,819 | posva | Read https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro and open a new issue with a finished repro on that jsfiddle | 2020-12-14T22:05:38 | 2020-12-14T22:05:38 | {} | MEMBER |
vuejs | core | 741,589,928 | 2,768 | 07akioni | > Repetitive description.
>
>
>
> And its really complicated.
repetitive desc is removed | 2020-12-09T07:29:58 | 2020-12-09T07:29:58 | {} | CONTRIBUTOR |
vuejs | core | 741,602,590 | 2,771 | edison1105 | see https://github.com/vuejs/jsx-next/issues/51 | 2020-12-09T07:59:18 | 2020-12-09T08:01:37 | {} | MEMBER |
vuejs | core | 741,696,586 | 2,768 | 07akioni | > I debugged this bug locally, but found it works. My local code is the latest master. so I think it's fixed by some commits.
> see demo: https://codesandbox.io/s/nervous-raman-2776d?file=/index.html
It works before `3.0.2`, fails in `3.0.3` & `3.0.4`.
So maybe finding the reason is crucial to make it not regres... | 2020-12-09T10:57:40 | 2020-12-09T11:16:20 | {} | CONTRIBUTOR |
vuejs | core | 741,713,053 | 2,768 | posva | yeah, PR welcome for a non regression test! | 2020-12-09T11:30:19 | 2020-12-09T11:30:19 | {} | MEMBER |
vuejs | core | 742,375,797 | 2,783 | posva | Closing as this is working as intended | 2020-12-10T08:49:14 | 2020-12-10T08:49:14 | {} | MEMBER |
vuejs | core | 742,845,589 | 2,431 | mome-borogove | > This is an intended change. v3 uses the equivalent of v2's whitespace: 'condense' in all cases, so whitespace between tags are only preserved if it contains no newlines
@yyx990803 I'd like to also weigh in on this not being an ideal behavior, especially as a default.
This ended up causing a lot of unfortunate b... | 2020-12-10T22:40:35 | 2020-12-10T22:40:35 | {
"+1": 2
} | NONE |
vuejs | core | 743,950,952 | 2,804 | HcySunYang | This has been fixed in https://github.com/vuejs/vue-next/commit/c59897c7b0dbd82b5bbf3fbca945c0639ac37fb8 | 2020-12-13T05:07:24 | 2020-12-13T05:07:24 | {} | MEMBER |
vuejs | core | 744,100,351 | 2,809 | Zcating | It is because of the override function.
```
export function ref<T extends object>(value: T): ToRef<T>
export function ref<T>(value: T): Ref<UnwrapRef<T>>
export function ref<T = any>(): Ref<T | undefined>
```
your code `const x = ref<{ a: Ref<number> } | undefined>();` will run as `ref<T = any>(): Ref<T | undefin... | 2020-12-14T00:37:49 | 2020-12-14T00:38:09 | {} | CONTRIBUTOR |
vuejs | core | 744,134,376 | 2,810 | HcySunYang | Please report the issue to element-plus first, or provide a minimal reproduce without element-plus. | 2020-12-14T02:56:12 | 2020-12-14T02:56:12 | {} | MEMBER |
vuejs | core | 744,206,000 | 982 | tcstory | > Why not on the d.ts use it ?
>
> (为什么不能在d.ts 中设置这个？)
>
> ```js
> declare module '@vue/runtime-core' {
> interface ComponentCustomProperties {
> $router: Router
> }
> }
> ```
I also want to known why I can not place the code in the shims-vue.d.ts. I had tried to place the code in shims-vue.d.ts... | 2020-12-14T06:32:36 | 2020-12-14T06:32:36 | {} | NONE |
vuejs | core | 741,625,897 | 2,777 | posva | Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2020-12-09T08:46:05 | 2020-12-09T08:46:05 | {} | MEMBER |
vuejs | core | 742,221,729 | 2,783 | Zcating | `document.getElementById` | 2020-12-10T03:53:45 | 2020-12-10T03:53:45 | {} | CONTRIBUTOR |
vuejs | core | 742,271,131 | 2,786 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-10T06:25:39 | 2020-12-10T06:25:39 | {} | NONE |
vuejs | core | 743,414,701 | 2,800 | posva | The problem is that you shouldn't have the `opacity-75` always set because it is defined after `opacity-0` and therefore has a higher priority. That's why there is no initial animation because the element has both classes and only opacity-75 is applied.
What you need to do is create another CSS selector that applies t... | 2020-12-11T20:37:24 | 2020-12-11T20:37:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 743,982,508 | 2,807 | posva | In order to use `async setup`, you need to use `<Suspense>`
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-12-13T10:06:37 | 2020-12-13T10:06:37 | {} | MEMBER |
vuejs | core | 744,103,137 | 2,809 | Zcating | But while changing `export function ref<T = any>(): Ref<T | undefined>` to `export function ref<T = any>(): Ref<UnwrapRef<T> | undefined>`, ref's setter shows the error setting type.
```
const x = ref<{ a: Ref<number> } | undefined>();
// ERROR Type 'Ref<number>' is not assignable to type 'number'.ts(2322)
x.value ... | 2020-12-14T00:48:46 | 2020-12-14T00:48:46 | {} | CONTRIBUTOR |
vuejs | core | 744,309,656 | 2,790 | luwuer | Also，resuing without ref assertion will change the `uid` of VNode of `div(hello)` . This seem not to be a principle of reuse. | 2020-12-14T09:32:30 | 2020-12-14T09:36:56 | {} | CONTRIBUTOR |
vuejs | core | 742,217,611 | 2,780 | HcySunYang | Hi @edison1105 , sorry, I didn’t notice your PR, but I just checked it. I think we need to add the flags to fragment correctly instead of letting it pass directly. | 2020-12-10T03:39:28 | 2020-12-10T03:39:28 | {} | MEMBER |
vuejs | core | 742,700,958 | 2,793 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-10T18:15:06 | 2020-12-10T18:15:06 | {} | NONE |
vuejs | core | 743,005,240 | 2,799 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-11T06:37:30 | 2020-12-11T06:40:48 | {} | NONE |
vuejs | core | 743,021,251 | 2,768 | 07akioni | > @07akioni
> `:show=“show”` Can you tell me what this means? What's the effect?
> I tried to change it to` v-show=“show”` and it responded normally.
> The `v-if="show"` can also respond.
> Whether the problem is caused by props value transfer or data binding is not determined.
The case is extract from a real co... | 2020-12-11T07:16:00 | 2020-12-11T07:16:00 | {} | CONTRIBUTOR |
vuejs | core | 743,986,081 | 2,730 | asv7c2 | Looks like it by design. [doc](https://v3.vuejs.org/guide/reactivity-computed-watchers.html#effect-flush-timing) | 2020-12-13T10:38:57 | 2020-12-13T10:38:57 | {} | NONE |
vuejs | core | 744,020,647 | 2,807 | kadiryazici | I already tried `Suspense` tho and didn't work | 2020-12-13T15:06:05 | 2020-12-13T15:06:05 | {} | CONTRIBUTOR |
vuejs | core | 744,060,105 | 2,808 | ycmjason | oops thanks! | 2020-12-13T19:59:23 | 2020-12-13T19:59:23 | {} | CONTRIBUTOR |
vuejs | core | 744,298,320 | 2,790 | luwuer | ### How does Vue trigger this problem ?
| 2020-12-14T09:13:57 | 2020-12-14T09:20:40 | {} | CONTRIBUTOR |
vuejs | core | 744,985,164 | 2,820 | luwuer | Same as #2715 and closed by #2717 | 2020-12-15T01:42:58 | 2020-12-15T01:42:58 | {} | CONTRIBUTOR |
vuejs | core | 741,767,816 | 2,768 | 07akioni | > @posva
> I am sorry, When writing test cases, I found that there was a problem with my demo above, and I updated the code again.Latest demo: https://codesandbox.io/s/nervous-raman-2776d?file=/index.html
> This bug still exists.Maybe we should reopen this issues.
> I apologize for my mistake.
>
> > It works befo... | 2020-12-09T13:23:26 | 2020-12-09T13:23:26 | {} | CONTRIBUTOR |
vuejs | core | 742,372,573 | 2,783 | 07akioni | As a workaround, you can use a custom directive to get the element of the inner vNode (you need to write render function if it is a slot).
```js
// using render function
import { withDirectives, h, Teleport } from 'vue'
const dir = {
mounted (el) {
console.log(el)
},
updated (el) {
console.lo... | 2020-12-10T08:42:55 | 2020-12-10T08:49:54 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 741,717,060 | 2,778 | posva | Read the link I sent you at https://github.com/vuejs/vue-next/issues/2776#issuecomment-741623315:
- **a minimal reproduction**, no TS, no vant, no class component, etc
- Write it in English so everybody can understand | 2020-12-09T11:39:01 | 2020-12-09T11:39:01 | {} | MEMBER |
vuejs | core | 741,768,449 | 2,564 | 07akioni | > Tried locally and this works correctly. @07akioni make sure to test locally next time! You can download a zip from codesandbox to make sure the correct versions are used, sometimes there are cache issues on CS
You are right, I'm sorry for that. The problem is solved.
Next time I'll test it locally too. Thanks f... | 2020-12-09T13:24:39 | 2020-12-09T13:25:13 | {} | CONTRIBUTOR |
vuejs | core | 741,703,663 | 2,564 | 07akioni | @posva @yyx990803
<del>The problem seems not to be solved?</del>
<del>The behavior still doesn't work as expected in the reproduction link.</del> | 2020-12-09T11:11:19 | 2020-12-09T13:25:24 | {} | CONTRIBUTOR |
vuejs | core | 742,998,188 | 2,768 | Mr14huashao | @07akioni
`:show=“show”` Can you tell me what this means? What's the effect?
I tried to change it to` v-show=“show”` and it responded normally.
The `v-if="show"` can also respond.
Whether the problem is caused by props value transfer or data binding is not determined. | 2020-12-11T06:19:52 | 2020-12-11T06:19:52 | {} | NONE |
vuejs | core | 743,004,918 | 2,797 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-11T06:36:45 | 2020-12-11T06:36:45 | {} | NONE |
vuejs | core | 743,734,104 | 2,803 | posva | I don't think this is a good idea: https://github.com/vuejs/vue-next/issues/2801#issuecomment-743733805
Note changing attributes once the element is already in the dom does nothing for many elements (e.g. input's `value`) | 2020-12-12T10:13:05 | 2020-12-12T10:13:05 | {} | MEMBER |
vuejs | core | 744,058,548 | 2,808 | jacekkarczmarczyk | https://github.com/vuejs/vue-next/blob/master/CHANGELOG.md#breaking-changes-1 | 2020-12-13T19:46:21 | 2020-12-13T19:46:21 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 744,149,891 | 2,790 | qq397023775 | > But the root cause i think is incorrect element reusing when patch
@luwuer
This problem has nothing to do with `patch`, please note that we have already had the issue in the `onMounted` hook, and no patch has been performed yet. | 2020-12-14T03:58:11 | 2020-12-14T03:58:23 | {} | NONE |
vuejs | core | 744,163,149 | 2,790 | luwuer | Hook `mounted` is trigger after `patch`.
https://github.com/vuejs/vue-next/blob/07559e5dd7e392c415d098f75ab4dee03065302e/packages/runtime-core/src/renderer.ts#L1342-L1395 | 2020-12-14T04:47:19 | 2020-12-14T04:51:01 | {} | CONTRIBUTOR |
vuejs | core | 744,202,527 | 2,790 | luwuer | > Completely wrong, the patch here refers to the update triggered after changing the reactive data. the `mounted` is always before the `updated`.
Its ok `mounted` before `update`.
But there one thing i didnt make clear that the `refDom.value` is correct when `mounted` (alreay patch), and go wrong when
patch befor... | 2020-12-14T06:25:58 | 2020-12-14T06:27:06 | {} | CONTRIBUTOR |
vuejs | core | 741,866,949 | 2,781 | posva | Read https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2020-12-09T15:57:55 | 2020-12-09T15:57:55 | {} | MEMBER |
vuejs | core | 743,046,457 | 2,246 | gigasource | Hi, any fix for this bug ? | 2020-12-11T08:18:04 | 2020-12-11T08:18:04 | {} | NONE |
vuejs | core | 743,117,653 | 2,790 | qq397023775 | Please reopen this issue, wait @yyx990803 to check it. | 2020-12-11T10:38:54 | 2020-12-11T10:38:54 | {} | NONE |
vuejs | core | 743,913,500 | 1,539 | iassasin | Ran in same issue. It was very useful feature: SFC with render function + scoped style. Is there any plans when it will be implemented in vue3? | 2020-12-12T22:22:58 | 2020-12-12T22:22:58 | {
"+1": 9
} | NONE |
vuejs | core | 744,226,675 | 2,814 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-14T07:14:36 | 2020-12-14T07:14:36 | {} | NONE |
vuejs | core | 744,571,218 | 2,819 | lukaskoeller | #### Issues with the same error:
- #2620
- #1704
#### Closed PRs related to this issue:
- #1724
#### Question on Discord:
- [Vue Land #composition-api](https://discord.com/channels/325477692906536972/713147202188607558/788042888990162954) | 2020-12-14T16:54:30 | 2020-12-14T17:03:36 | {} | NONE |
vuejs | core | 741,713,735 | 2,751 | sapphi-red | I think you should change it to `SetupContext<any>` if you want to be able to emit any event.
```ts
function myFn({ emit }: SetupContext<any>) {
emit('sth', ...);
}
```
If you want to limit it to 'sth' event, do it like below.
```ts
function myFn({ emit }: SetupContext<{ sth: (params: any) => any }>) {
... | 2020-12-09T11:31:43 | 2020-12-09T11:31:43 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 741,760,075 | 2,768 | edison1105 | @posva
I am sorry, When writing test cases, I found that there was a problem with my demo above, and I updated the code again.Latest demo: https://codesandbox.io/s/nervous-raman-2776d?file=/index.html
This bug still exists.Maybe we should reopen this issues.
I apologize for my mistake.
> It works before 3.0.2... | 2020-12-09T13:10:27 | 2020-12-09T13:18:42 | {} | MEMBER |
vuejs | core | 743,733,805 | 2,801 | posva | it's because in Vue 3, attributes are set as properties: `el.width = ...` instead of `el.setAttribute()` if they can be set. For this specific case, one should use the style width and height, which are more appropriate.
Note that even the attribute should be in pixels without unit: https://developer.mozilla.org/en-U... | 2020-12-12T10:09:54 | 2020-12-12T10:09:54 | {} | MEMBER |
vuejs | core | 744,150,399 | 2,779 | edison1105 | see https://github.com/vuejs/jsx-next | 2020-12-14T04:00:23 | 2020-12-14T04:00:23 | {} | MEMBER |
vuejs | core | 744,224,476 | 2,793 | dependabot-preview[bot] | Superseded by #2811. | 2020-12-14T07:10:27 | 2020-12-14T07:10:27 | {} | CONTRIBUTOR |
vuejs | core | 745,079,912 | 2,825 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-15T06:20:00 | 2020-12-15T06:23:31 | {} | NONE |
vuejs | core | 742,212,678 | 2,780 | edison1105 | v3.0.3 is works fine.caused by 3bc2914e32b030b1247659f871f6055827154087 | 2020-12-10T03:25:50 | 2020-12-10T03:25:50 | {} | MEMBER |
vuejs | core | 742,483,429 | 2,789 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
See https://v3.vuejs.org/api/options-data.html#emits fo... | 2020-12-10T12:12:29 | 2020-12-10T12:12:29 | {} | MEMBER |
vuejs | core | 743,005,161 | 2,798 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-11T06:37:19 | 2020-12-11T06:37:19 | {} | NONE |
vuejs | core | 743,770,773 | 2,805 | 2nthony | Duplicate #2804 | 2020-12-12T15:19:25 | 2020-12-12T15:19:25 | {} | NONE |
vuejs | core | 743,915,847 | 1,925 | davidmoshal | Many large US companies have legacy ActiveX components which require IE11,
and which are not going to be replaced anytime soon.
So, given the choice of a single browser to support, they choose IE11. | 2020-12-12T22:45:46 | 2020-12-12T22:45:46 | {} | NONE |
vuejs | core | 744,125,973 | 2,779 | ht-sauce | > 也许这不是Vue的错误，所以我关闭了PR。
> 作为工作场所，请像下面这样编辑babel.config.js：
>
> ```js
> 模块。出口 = {
> 预设：[
> '@ vue / cli-plugin-babel / preset'
> ] ，
> 插件：[
> / * eslint-disable-next-line global-require * /
> [要求（'@ vue / babel-plugin-jsx' ）， { isCustomElement：tag => / ^ ion- / 。测试（标签） } ] ，
> ] ，
... | 2020-12-14T02:24:08 | 2020-12-14T02:24:08 | {} | NONE |
vuejs | core | 744,148,052 | 2,790 | luwuer | The immediate reason is that `setRef` is async, so that the `refDom.value` has a preValue on the first frame.
https://github.com/vuejs/vue-next/blob/07559e5dd7e392c415d098f75ab4dee03065302e/packages/runtime-core/src/renderer.ts#L344-L358
You can change the `onMounted` callback like code blow to verify it in repro... | 2020-12-14T03:49:49 | 2020-12-14T06:31:29 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.