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 | 822,007,461 | 3,623 | yunbookf | > This seems to be more an issue caused by the element re-use between v-if and v-else. Adding a `key` can be used as a workaround:
>
> ```
> <div id="app">
> <div v-if="mode">
> Mode 1
> <teleport to="#pop" :disabled="dis">
> <div class="port" :key="1">
> Port 1
> <teleport to="#pop" :disab... | 2021-04-18T15:14:11 | 2021-04-18T15:14:11 | {} | NONE |
vuejs | core | 823,420,364 | 3,638 | posva | You should use a `shallowReactive` or `markRaw()` https://v3.vuejs.org/api/basic-reactivity.html#markraw to mark the element (or any other complex object) when passed to Vue. This will also improve the perf.
I don't think we should treat the DOM element in any special way. Maybe there is a way to document this so it... | 2021-04-20T16:29:02 | 2021-04-20T16:29:02 | {} | MEMBER |
vuejs | core | 823,791,893 | 3,640 | HcySunYang | You must use async setup with `Suspense` component https://codesandbox.io/s/hungry-bash-vczqp?file=/src/App.vue. Otherwise, `setup` cannot be async. | 2021-04-21T05:41:05 | 2021-04-21T05:41:05 | {} | MEMBER |
vuejs | core | 823,966,514 | 2,094 | bartenra | pikax helped me out on Discord with this snippet:
```ts
type Props<T> = T extends new () => { $props: infer P } ? P : never
```
I added a comment to your PR, I think it's a great addition but it should definitely be documented since these utility classes are meant for public consumption.
| 2021-04-21T10:47:52 | 2021-04-21T11:13:24 | {
"heart": 3
} | CONTRIBUTOR |
vuejs | core | 824,550,430 | 3,647 | hyf0 | some type programing maybe helpful. I guess this need tests and .d.ts tests, which I don't know how to do it and can't send PR to fix it.
```ts
export function effect<T = any, O extends ReactiveEffectOptions = typeof EMPTY_OBJ>(
fn: () => T,
options: O = (EMPTY_OBJ as O)
): O extends { scheduler?: undefined } ... | 2021-04-22T05:31:12 | 2021-04-22T05:31:12 | {} | CONTRIBUTOR |
vuejs | core | 820,372,746 | 3,610 | imaxing | > Please follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro and open a new issue with a boiled down reproduction.
>
> Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions!
sorry, I did it according to the prompts. What's wrong | 2021-04-15T12:08:45 | 2021-04-15T12:08:45 | {} | NONE |
vuejs | core | 824,895,528 | 3,646 | blayzen-w | Woops, I can't believe I missed that message for the directives. Thanks for pointing it out.
What about accessing properties on an undefined object? | 2021-04-22T14:33:04 | 2021-04-22T14:33:04 | {} | NONE |
vuejs | core | 818,405,108 | 3,566 | HcySunYang | @posva Is this issue the same as the one described by https://github.com/vuejs/vue-next/issues/2119? | 2021-04-13T03:31:32 | 2021-04-13T03:31:32 | {} | MEMBER |
vuejs | core | 818,452,747 | 3,422 | uniquejava | 楼主怎么解决的，我今天也碰到了。 突然间就坏了。 | 2021-04-13T05:39:23 | 2021-04-13T05:39:23 | {} | NONE |
vuejs | core | 818,616,380 | 3,594 | edison1105 | @CHOYSEN
I tried your repo and everything works fine. | 2021-04-13T10:05:27 | 2021-04-13T10:05:27 | {} | MEMBER |
vuejs | core | 818,648,608 | 3,590 | LinusBorg | Probably not. Wanted to check out why it was a problem on vue-cli durting testing with mocha though, before I close it. | 2021-04-13T11:03:34 | 2021-04-13T11:03:34 | {} | MEMBER |
vuejs | core | 819,595,259 | 2,753 | yangmingshan | So this PR pass `this.proxy` to `this.$watch()` and composition API `watch()`, but we shouldn't leak `this.proxy` to `setup()` right? | 2021-04-14T15:11:02 | 2021-04-14T15:42:36 | {} | CONTRIBUTOR |
vuejs | core | 819,819,576 | 3,031 | 99linesofcode | Yes so basically I ran into what I believe is the issue that l0rn is trying to raise here.
Given a vue-cli generated Vue 3 project, the typescript compiler will complain about the injected value not being present on the component when using TypeScript in combination with the Options API. Now, I might be missing some... | 2021-04-14T20:44:18 | 2021-04-14T20:44:18 | {} | NONE |
vuejs | core | 820,362,155 | 3,610 | posva | Please follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro and open a new issue with a boiled down reproduction.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-04-15T11:49:56 | 2021-04-15T11:49:56 | {} | MEMBER |
vuejs | core | 821,253,872 | 3,031 | JayDouglass | > Yes so basically I ran into what I believe is the issue that l0rn is trying to raise here.
>
> Given a vue-cli generated Vue 3 project, the typescript compiler will complain about the injected value not being present on the component when using TypeScript in combination with the Options API. Now, I might be missin... | 2021-04-16T15:23:59 | 2021-04-16T15:23:59 | {} | NONE |
vuejs | core | 821,966,406 | 3,623 | LinusBorg | This seems to be more an issue caused by the element re-use between v-if and v-else. Adding a `key` can be used as a workaround:
```html
<div id="app">
<div v-if="mode">
Mode 1
<teleport to="#pop" :disabled="dis">
<div class="port" :key="1">
Port 1
<teleport to="#pop" :disabled="dis">
... | 2021-04-18T10:00:12 | 2021-04-18T10:00:12 | {} | MEMBER |
vuejs | core | 821,976,601 | 3,623 | edison1105 | I don't think this has anything to do with element re-use, but rather the nested teleport not being unmounted correctly.
When the el of Port1 was removed, Port2 was not removed correctly because it was m... | 2021-04-18T11:28:14 | 2021-04-19T01:14:07 | {} | MEMBER |
vuejs | core | 822,977,657 | 3,628 | HcySunYang | > Documentation of v-model binding to Sets.
If I remember correctly, we already have some ideas about documentation
> Explicit v-model syntax/option for multiple element values -> single Array behaviour?
Why are you surprised? Regardless of other aspects, consider how the browser sends form data? And how does ... | 2021-04-20T05:10:12 | 2021-04-20T05:10:12 | {
"+1": 2
} | MEMBER |
vuejs | core | 823,712,297 | 3,631 | lidlanca | @hisland, `lzut8.decompress` expects an lz compressed input, regardless of the encoding . URLs that were generated by `btoa`, when decoded will not be compressed, and the decompressed value is likely to be invalid. | 2021-04-21T01:40:28 | 2021-04-21T01:40:28 | {} | CONTRIBUTOR |
vuejs | core | 823,928,167 | 2,303 | samllLuck | vue是支持运行时编译的，但是你可能用了插件，导致报错，具体解决方案，可参考https://blog.csdn.net/qq_41499782/article/details/112505665，亲测有效 | 2021-04-21T09:41:45 | 2021-04-21T09:41:45 | {
"+1": 1
} | NONE |
vuejs | core | 824,020,501 | 2,027 | WalkAlone0325 | You can specify `watch(route.xx)`,So you don't have to `deep: true`,i try it's OK. | 2021-04-21T12:27:31 | 2021-04-21T12:27:31 | {} | CONTRIBUTOR |
vuejs | core | 824,542,084 | 3,647 | HcySunYang | Please double-check the reproduction you provided, it cannot reproduce the problem you described. | 2021-04-22T05:08:31 | 2021-04-22T05:08:31 | {} | MEMBER |
vuejs | core | 818,606,420 | 3,594 | posva | Please open an issue in element-plus first.
Read https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro and open an issue here if you reproduce it without element-plus | 2021-04-13T09:49:30 | 2021-04-13T09:49:49 | {} | MEMBER |
vuejs | core | 819,277,714 | 3,594 | CHOYSEN | @edison1105
It may cause by element-plus. I'm not sure.
| 2021-04-14T06:55:59 | 2021-04-14T07:59:53 | {} | CONTRIBUTOR |
vuejs | core | 819,518,957 | 3,601 | LinusBorg | The prop is not meant to change the duration specified in your CSS. It defines when the transition component will consider the transition to be finished and trigger the end evenrts (afterAppear, afterEnter, afterLeave).
```vue
<template>
<transition name="fade" :duration="5000" @afterEnter="end">
<p v-if="s... | 2021-04-14T13:29:27 | 2021-04-14T13:32:57 | {} | MEMBER |
vuejs | core | 819,939,004 | 2,753 | edison1105 | > So this PR pass `this.proxy` to `this.$watch()` and composition API `watch()`, but we shouldn't leak `this.proxy` to `setup()` right?
oh, my fault. | 2021-04-15T00:42:43 | 2021-04-15T00:42:43 | {} | MEMBER |
vuejs | core | 821,828,776 | 3,620 | edison1105 | close this one because #3622 is better. | 2021-04-17T14:10:44 | 2021-04-17T14:10:44 | {} | MEMBER |
vuejs | core | 822,198,888 | 3,627 | HcySunYang | If `tag` is a custom element, it will be treated as-is, what is your real intention? can you provide a repro? | 2021-04-19T06:14:29 | 2021-04-19T06:14:29 | {} | MEMBER |
vuejs | core | 823,728,912 | 3,638 | Sociosarbis | As there is already a previous case involved environment specific code, "determine an object is intanceof Node" could be accpected.
But when we changed the code to:
```js
app.component('comp-2', {
template: `<input :value="value" />`,
props: {
value: Number
},
setup() {
}
})
app.component('c... | 2021-04-21T02:32:29 | 2021-04-21T02:33:28 | {} | NONE |
vuejs | core | 818,460,564 | 3,422 | uniquejava | I fixed it!. FYI if someone later met this issue
1. Terminal: `npx vite --force`
2. Chrome dev tools: Network => Check `Disable cache`.
3. Hard refresh page
This occurs when I refactor my project to use the `script setup sugar`. | 2021-04-13T05:57:54 | 2021-04-13T05:57:54 | {} | NONE |
vuejs | core | 818,610,436 | 3,593 | Edge00 | Sorry... | 2021-04-13T09:56:02 | 2021-04-13T09:56:02 | {} | NONE |
vuejs | core | 819,280,201 | 3,596 | phanan | That makes perfect sense @posva. The two bindings with conflicting effects should have a warning. Binding vs static shouldn't. | 2021-04-14T07:00:49 | 2021-04-14T07:20:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 819,584,372 | 3,602 | cathrinevaage | So clearly something weird happened with that link, here it is again, hopefully working this time.
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbiAgaW1wb3J0IHsgZGVmaW5lQ29tcG9uZW50LCBjb21wdXRlZCwgcmVhY3RpdmUsIHJlZiwgd2F0Y2hFZmZlY3QsIHJlYWRvbmx5IH0gZnJvbSAndnVlJ1xuICBcbiAgZXhwb3J0IGRlZmF1bHQgZGVmaW5lQ29tcG9uZW5... | 2021-04-14T14:56:33 | 2021-04-14T14:56:33 | {} | CONTRIBUTOR |
vuejs | core | 819,749,316 | 3,604 | HcySunYang | This solution is flawed, but I am going to bed. Wait for me to wake up and fix it 😅 | 2021-04-14T18:44:54 | 2021-04-14T18:44:54 | {
"laugh": 1
} | MEMBER |
vuejs | core | 820,178,838 | 1,791 | yaquawa | Hi, had any progress on this?? or any plan to implement this in the future or not?
It was possible on Vue2, now how to do this on Vue3? | 2021-04-15T07:15:00 | 2021-04-15T07:17:16 | {} | NONE |
vuejs | core | 820,343,928 | 3,609 | manusis | Can you guide me in the right direction? In our case, most components do not have a fixed template but are used only provide props and methods to the inner html template but some components do have a default template. | 2021-04-15T11:16:29 | 2021-04-15T11:16:29 | {} | NONE |
vuejs | core | 820,357,236 | 3,609 | posva | @manusis use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-04-15T11:40:40 | 2021-04-15T11:40:40 | {} | MEMBER |
vuejs | core | 825,009,488 | 3,399 | johnsoncodehk | Will this PR add `v-on` modifiers?
https://v3.vuejs.org/api/directives.html#v-on | 2021-04-22T16:47:25 | 2021-04-22T16:47:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 735,606,497 | 2,689 | posva | Vue 3 supports typescript out of the box. It doesn't require class or decorator usage but you can with the mentioned libraries if you want to.
The reasoning behind this has been extensively discussed during the composition API RFC. You can take a look at the rfcs repo to read about it | 2020-11-30T07:29:49 | 2020-11-30T07:29:49 | {} | MEMBER |
vuejs | core | 735,734,070 | 2,689 | edison1105 | You can take a look at this if you are interested. https://github.com/vuejs/rfcs/pull/17
and https://github.com/vuejs/rfcs/pull/17#issuecomment-494242121 | 2020-11-30T11:39:41 | 2020-11-30T11:41:43 | {} | MEMBER |
vuejs | core | 737,090,641 | 2,709 | ChanningHan | 可惜 | 2020-12-02T08:59:25 | 2020-12-02T08:59:25 | {} | NONE |
vuejs | core | 737,705,179 | 2,711 | meteorlxy | My previous comment was wrong.
The ref is still `undefined` during SSR, it's only available after mounted.
So it should not be extracted to ctx. | 2020-12-03T06:51:41 | 2020-12-03T07:11:25 | {} | MEMBER |
vuejs | core | 736,093,518 | 2,648 | yyx990803 | > I've added a test but still i'm a bit confused about the way Teleport works because:
>
> * in my tests, i needed to add a v-if or disabled prop to the Teleport component because i otherwise get an error saying the destination is invalid; that's not the behaviour i get when trying it out outside of a test;
> * it ... | 2020-11-30T22:26:34 | 2020-11-30T22:26:34 | {} | MEMBER |
vuejs | core | 736,427,612 | 2,597 | posva | What I meant is that `-active` should be set on the first frame, as it is right now. The change you want to do is a breaking change and won't happen | 2020-12-01T11:06:32 | 2020-12-01T11:06:32 | {} | MEMBER |
vuejs | core | 736,671,923 | 2,700 | yyx990803 | closed via 83a79a82 | 2020-12-01T16:42:05 | 2020-12-01T16:42:05 | {} | MEMBER |
vuejs | core | 737,017,630 | 2,707 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.42 KB (0%) |
| runtime-dom.global.prod.js | 26.73 KB (0%) |
| size-check.global.prod.js | 16.18 KB (0%) | | 2020-12-02T06:15:45 | 2020-12-02T06:15:45 | {} | NONE |
vuejs | core | 732,747,868 | 2,195 | antfu | Convert back to draft as it misaligns with the latest RFC changes: https://github.com/vuejs/rfcs/pull/212#issuecomment-732746268
Still collecting feedback before implementing them. | 2020-11-24T08:46:16 | 2020-12-03T03:57:20 | {} | MEMBER |
vuejs | core | 736,288,646 | 2,694 | posva | @edison1105 yes, that's normal. With sets and arrays, there should be a value attribute instead | 2020-12-01T07:47:59 | 2020-12-01T07:47:59 | {} | MEMBER |
vuejs | core | 736,585,674 | 2,694 | edison1105 | Because `true-value` or `false-value` is not assigned to the `checkbox` after first rendered.
| 2020-12-01T14:27:10 | 2020-12-01T14:27:10 | {} | MEMBER |
vuejs | core | 736,671,807 | 2,700 | yyx990803 | I think reverting makes sense since the breakage is bigger than expected.
However, the issue raised in #2662 will need to be clearly documented as a caveat (/cc @vuejs/docs) - I couldn't find a way to detect the case and emit a runtime warning (we should probably still try to find a way to warn against this). | 2020-12-01T16:41:55 | 2020-12-01T16:41:55 | {} | MEMBER |
vuejs | core | 736,838,153 | 2,702 | posva | By setting the value to `false`, you are not changing it, resulting in the checkbox being checked by the browser but Vue not updating anything. If you set the initial value to 0 you will see the checkbox remains unchecked.
You need to force the element value in this specific scenario:
```js
const app = Vue.creat... | 2020-12-01T21:41:19 | 2020-12-01T21:41:19 | {} | MEMBER |
vuejs | core | 736,923,429 | 2,696 | edison1105 | > Sorry, I just saw this after I pushed [48f00c0](https://github.com/vuejs/vue-next/commit/48f00c0f1b574a235be40c560d2cf373be97615e) (note it just moves the `setChecked` call)
@yyx990803
I know this and tested it already. Unfortunately this is not working.
We should assign `true-value` or `false-value` to `check... | 2020-12-02T01:16:49 | 2020-12-02T01:16:49 | {} | MEMBER |
vuejs | core | 737,117,692 | 2,597 | luwuer | How about this way @posva
Disable transition on the first frame and enable it on the next frame. | 2020-12-02T09:48:11 | 2020-12-02T09:49:00 | {} | CONTRIBUTOR |
vuejs | core | 737,452,998 | 2,597 | yyx990803 | Note: I removed the transition disabling for enter/appear transitions because it breaks `v-show`'s current behavior. Whether we should or how to support `visibility: hidden` in transitions should be a separate discussion/PR. | 2020-12-02T19:42:24 | 2020-12-02T19:42:24 | {} | MEMBER |
vuejs | core | 737,524,165 | 2,708 | 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-... | 2020-12-02T22:05:43 | 2020-12-02T22:05:43 | {} | CONTRIBUTOR |
vuejs | core | 736,229,341 | 2,695 | soc221b | Adjust following code works for me.
before:
```css
...
.list-complete-item {
transition: all 0.8s ease;
display: inline-block;
margin-right: 10px;
}
...
```
after:
```css
.list-complete-item {
display: inline-block;
margin-right: 10px;
}
.list-complete-move {
transition: all 3s e... | 2020-12-01T05:29:31 | 2020-12-01T05:29:31 | {
"+1": 1
} | NONE |
vuejs | core | 736,261,152 | 2,698 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/11134?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2020-12-01T06:48:21 | 2020-12-01T06:48:21 | {} | CONTRIBUTOR |
vuejs | core | 736,527,715 | 2,597 | posva | Maybe this is clearer: https://v3.vuejs.org/guide/transitions-enterleave.html#transition-classes
Changing how the classes are added is a breaking change | 2020-12-01T12:41:41 | 2020-12-01T12:41:41 | {} | MEMBER |
vuejs | core | 736,687,895 | 2,696 | yyx990803 | Sorry, I just saw this after I pushed 48f00c0f (note it just moves the `setChecked` call) | 2020-12-01T17:05:50 | 2020-12-01T17:05:50 | {} | MEMBER |
vuejs | core | 737,659,273 | 2,711 | hoiheart | > * With ref target, teleports can find the target in current component scope, so it's rendered to string directly.
@meteorlxy
If so, I would like to get results that include circle in the renderToString.
| 2020-12-03T04:33:24 | 2020-12-03T04:33:24 | {} | NONE |
vuejs | core | 735,731,685 | 2,689 | edison1105 | I can also understand your thoughts very well. For back-end development, using classes, factories, decorators, etc. has become a habit (I am also very inclined to your opinion). Vue3 also tried the class api at the beginning, but finally gave up, partly because there are many features that are still in the proposal sta... | 2020-11-30T11:34:05 | 2020-11-30T11:34:05 | {} | MEMBER |
vuejs | core | 735,766,043 | 2,691 | posva | Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂 | 2020-11-30T12:48:55 | 2020-11-30T12:48:55 | {} | MEMBER |
vuejs | core | 735,908,176 | 2,692 | Jack-rainbow | [Properly demonstrate the demo](https://codepen.io/jack-rainbow/pen/wvzaMLp) | 2020-11-30T16:53:07 | 2020-11-30T16:53:07 | {} | NONE |
vuejs | core | 736,164,877 | 2,692 | Jack-rainbow | > 
>
> Seems to work. Maybe you have some extension blocking the link from alicdn
I did not block the link of alicdn, I solved it with SVG2.However, SVG1 has not been solved. I... | 2020-12-01T01:54:00 | 2020-12-01T01:54:00 | {} | NONE |
vuejs | core | 736,300,083 | 2,699 | CHOYSEN | Maybe we should remove this?
https://github.com/vuejs/vue-next/blob/4307610c35255477125c12217be514da068bedb0/packages/compiler-sfc/src/compileScript.ts#L813 | 2020-12-01T08:11:29 | 2020-12-01T08:11:29 | {} | CONTRIBUTOR |
vuejs | core | 736,689,150 | 2,696 | yyx990803 | It does occur to me that `true-value` and `false-value` are not properly handled for SSR. | 2020-12-01T17:07:46 | 2020-12-01T17:07:46 | {} | MEMBER |
vuejs | core | 737,432,116 | 2,513 | zauan | From what you experience, this is the same issue | 2020-12-02T19:02:27 | 2020-12-02T19:02:27 | {} | NONE |
vuejs | core | 735,580,753 | 2,690 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.22 KB (0%) |
| runtime-dom.global.prod.js | 26.57 KB (0%) |
| size-check.global.prod.js | 16.09 KB (0%) | | 2020-11-30T06:32:27 | 2020-11-30T06:32:27 | {} | NONE |
vuejs | core | 736,283,467 | 2,689 | John0King | @edison1105 sorry that I `@` for wrong person, I should @posva instead. | 2020-12-01T07:36:42 | 2020-12-01T07:36:42 | {} | NONE |
vuejs | core | 736,301,140 | 2,694 | edison1105 | > @edison1105 yes, that's normal. With sets and arrays, there should be a value attribute instead
Got it,Thanks~ | 2020-12-01T08:13:38 | 2020-12-01T08:13:38 | {} | MEMBER |
vuejs | core | 736,842,862 | 2,695 | LinusBorg | I'll reopen to investigate | 2020-12-01T21:51:01 | 2020-12-01T21:51:01 | {} | MEMBER |
vuejs | core | 736,861,387 | 2,695 | posva | This is the same in Vue 2 and likely to be related to how different browser engines compute the positions | 2020-12-01T22:30:06 | 2020-12-01T22:30:06 | {} | MEMBER |
vuejs | core | 737,038,040 | 2,706 | anotherso1a | I have used command `yarn test` and `yarn test --ci` locally, and it's work well, could you retry this failed CI ?
| 2020-12-02T07:04:11 | 2020-12-02T07:04:11 | {} | NONE |
vuejs | core | 737,716,921 | 2,713 | ryan0562 | 加载的巨慢......跟vue2官网天壤之别 | 2020-12-03T07:19:28 | 2020-12-03T07:19:28 | {} | NONE |
vuejs | core | 736,100,872 | 2,663 | yyx990803 | This is a necessary fix, however it unfortunately will lead to a minor breaking change:
```js
const App = {
watch:{
checkedNames() {
console.log('changed!')
}
},
data() {
return {
checkedNames: []
}
}
}
```
In this case the watcher will no longer fire because in v3... | 2020-11-30T22:45:07 | 2020-11-30T22:45:07 | {} | MEMBER |
vuejs | core | 736,672,986 | 2,662 | yyx990803 | See #2700 - unfortunately this will be considered a usage caveat for now, since `v-model` by design always replaces the original value, so use of a ref or a nested object property (e.g. `v-model="state.foo"`) is required. | 2020-12-01T16:43:49 | 2020-12-01T16:43:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 736,929,196 | 2,097 | mannymu |
import { createVNode ,render} from 'vue'
const body = document.body;
const root = document.createElement("div");
body.appendChild(root);
root.className = "custom-root";
export default {
install(app){
let div = document.createElement("div");
root.appendChild(div);
... | 2020-12-02T01:34:35 | 2020-12-02T01:34:35 | {
"+1": 1
} | NONE |
vuejs | core | 737,003,381 | 2,706 | edison1105 | This will conflict with https://github.com/vuejs/vue-next/pull/2447/files#diff-90e903ce16b300854d617842aaf5307c203aa6080fbcdf27e8b1260023527960
Maybe also need to check `ShadowRoot` | 2020-12-02T05:38:06 | 2020-12-02T05:38:06 | {} | MEMBER |
vuejs | core | 736,034,317 | 2,584 | yyx990803 | Thanks for the PR - see 3cd30c52 for a simpler fix. | 2020-11-30T20:49:00 | 2020-11-30T20:49:00 | {} | MEMBER |
vuejs | core | 736,127,481 | 2,671 | yyx990803 | `ref` on async component should be fixed by the commit above, but since it's async, you can't just access `this.$el` in mounted anyway. You'll have to wait until the async component is actually loaded (which can take unknown amount of time). So you should use a `ref` (after the fix is released). | 2020-12-01T00:00:56 | 2020-12-01T00:00:56 | {} | MEMBER |
vuejs | core | 736,274,025 | 2,220 | bhabgs | Each time the type is set, the project vue needs to be restarted to recognize the type。
| 2020-12-01T07:16:51 | 2020-12-01T07:17:41 | {} | NONE |
vuejs | core | 736,275,939 | 2,689 | edison1105 | > @edison1105 I read that a few month ago, that's why I open a new issue instead of talking in that closed issue again.
> and it seems that you and your team is hate `class` for some reason, but IMO I like `class` because it provide best language feature and most consistent API surface (there no other way to describe ... | 2020-12-01T07:20:48 | 2020-12-01T07:20:48 | {} | MEMBER |
vuejs | core | 736,511,820 | 2,597 | luwuer | > What I meant is that `-active` should be set on the first frame, as it is right now. The change you want to do is a breaking change and won't happen
Well, i am not understand why its breaking change, there has no change about external APIs.
I think about it another way just now:
1. Add a workaround class at ... | 2020-12-01T12:08:50 | 2020-12-01T12:13:24 | {} | CONTRIBUTOR |
vuejs | core | 736,574,066 | 2,694 | edison1105 | Hi @posva
I think this is not about inverted value. see https://codesandbox.io/s/fast-worker-k8q0e?file=/src/App.vue
I modified the code to see the problem more clearly. | 2020-12-01T14:08:00 | 2020-12-01T14:08:00 | {} | MEMBER |
vuejs | core | 736,841,899 | 2,695 | zlu883 | After further testing, I found that moving the transition property to the move class fixes transition on Chrome (v86). However, the issue persists on Firefox (v82) even with the move class. | 2020-12-01T21:48:56 | 2020-12-01T21:48:56 | {} | NONE |
vuejs | core | 737,374,523 | 2,520 | yyx990803 | Thanks for the PR. A cleaner fix is to simply never invoke the stale callbacks, see eaf8a67c | 2020-12-02T17:19:52 | 2020-12-02T17:19:52 | {} | MEMBER |
vuejs | core | 737,465,619 | 2,513 | zauan | @yyx990803 Looking at the source code, I noticed this comment accompanied the "fix" that introduced the problem above:
```
// async edge case #6566: inner click event triggers patch, event handler
// attached to outer element during patch, and triggered again. This
// happens because ... | 2020-12-02T20:06:47 | 2020-12-02T20:13:59 | {
"+1": 2
} | NONE |
vuejs | core | 737,714,454 | 2,713 | meteorlxy | https://v3.cn.vuejs.org/api/
https://github.com/vuejs/docs-next-zh-cn | 2020-12-03T07:13:32 | 2020-12-03T07:15:39 | {} | MEMBER |
vuejs | core | 736,266,591 | 2,609 | fangbinwei | The problem has been solved in vue-loader, so close | 2020-12-01T07:00:39 | 2020-12-01T07:00:39 | {} | NONE |
vuejs | core | 736,651,417 | 2,701 | IlCallo | Sure, didn't know there were a separate repo | 2020-12-01T16:08:46 | 2020-12-01T16:08:46 | {} | NONE |
vuejs | core | 736,904,944 | 2,695 | zlu883 | From my experience most browsers don't like transitions being changed midway and may visually glitch unless you force a layout reflow (e.g. by doing a computed property access) at the right timing, which might be subtly different between browsers. This might be related to this issue.
I'm personally fine with it work... | 2020-12-02T00:21:53 | 2020-12-02T00:42:26 | {} | NONE |
vuejs | core | 737,544,553 | 2,642 | Asylian21 | There is lot of people waiting for major support of PostCSS (beacuse of tailwindcss) | 2020-12-02T22:52:59 | 2020-12-02T22:52:59 | {} | NONE |
vuejs | core | 737,640,211 | 2,694 | edison1105 | > `model` should be the source of truth, not the template. If the user intends to provide an initial value that is neither true-value or false-value, the value should be left untouched.
>
> This actually has nothing to do with `true/false-value`. e.g. if you have `<input type="checkbox" v-model="model">` but `model`... | 2020-12-03T03:22:46 | 2020-12-03T03:22:46 | {} | MEMBER |
vuejs | core | 737,680,687 | 2,712 | crutchcorn | I have just ran this same issue against `2.6.12` and confirmed that it does indeed work:
https://codepen.io/crutchcorn/pen/oNzjOGm | 2020-12-03T05:45:13 | 2020-12-03T05:45:13 | {} | NONE |
vuejs | core | 736,070,407 | 2,632 | yyx990803 | Thanks for the PR, but the fix can be simpler - see e4f09c14 | 2020-11-30T21:34:40 | 2020-11-30T21:34:40 | {} | MEMBER |
vuejs | core | 736,164,234 | 2,692 | Jack-rainbow | > As far as i can make out, your demo works fine. The "House" SVG is displayed correctly. Am I missing something?
You haven't missed anything. Maybe my operation and description are not very clear.Thank you for your answer | 2020-12-01T01:51:48 | 2020-12-01T01:51:48 | {} | NONE |
vuejs | core | 736,284,609 | 2,689 | edison1105 | > @edison1105 sorry that I `@` for wrong person, I should @posva instead.
oh~ ,this is more embarrassing.😆😆😆 | 2020-12-01T07:39:14 | 2020-12-01T07:39:14 | {} | MEMBER |
vuejs | core | 736,292,410 | 2,695 | LinusBorg | ...and that is also how the CSS in the docs is explained and presented - the `transition` property is always to be defined on the `-move` class.
With that, I don't see any jumping occurring and think we can close this as there's nothing to fix. | 2020-12-01T07:56:05 | 2020-12-01T07:56:05 | {} | MEMBER |
vuejs | core | 736,672,194 | 2,663 | yyx990803 | Note: this has been reverted in 83a79a82 (ref: #2700) | 2020-12-01T16:42:34 | 2020-12-01T16:42:34 | {} | MEMBER |
vuejs | core | 737,587,509 | 2,694 | edison1105 | Hi @posva @yyx990803
I update demo https://codesandbox.io/s/fast-worker-k8q0e?file=/src/App.vue with lastest vue-next version `3.0.4`.
This bug still happens.I think the `model value` should be `22` on initial render. | 2020-12-03T00:51:35 | 2020-12-03T00:51:35 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.