same code, < input type= "text" v Melody model = "aa" @ input= "aa = aa.replace (/\ DMag,"")" >
version 2.5 will still instantly display the input and then match it, while 2.4 will not show the matching content
same code, < input type= "text" v Melody model = "aa" @ input= "aa = aa.replace (/\ DMag,"")" >
version 2.5 will still instantly display the input and then match it, while 2.4 will not show the matching content
what a coincidence! I happen to be writing the article Vue Source Code Reading-batch Asynchronous updates and nextTick principles , which happens to involve the content of this piece ~
.this situation is also annotated in the source code of vue. You can click in and have a look, so the version after 2.5 has changed this situation. I will translate it here:
.in versions prior to 2.4, nextTick was basically based on microtask, but in some cases microtask has too high priority
and may be triggered between successive sequential events (for example,# 4521,# 6690) or even during event bubbling of the same event (# 6566).
but if all of them are changed to macrotask, it will also have a performance impact on some scenes with redrawing and animation, such as issue-sharp6813.
the workaround provided here is to use microtask, by default but to force the use of macrotask when needed (for example, in event handlers attached to v-on)
so it will not be displayed before 2.4because of the dom event previously implemented using microtask, which is executed before patch after the macro task execution of the current tick, so I guess it is because the microtask high priority reason does not wait for the current tick change patch to render to the real dom has changed the data, so of course it will not be rendered to the real DOM.
the nextTick after 2.5 uses macrotask, as a callback that is sure to be executed after the next tick, so the content entered by the input will naturally be rendered to the real dom before the callback is executed, so what you see is a flash ~
so? What's your problem? Shouldn't you look at the source code and analyze the reasons?
and don't write this. If you bind < input > to aa , you should
data() {
return {
_aa: '',
}
},
computed: {
aa: {
get() {
return this._aa;
},
set(value) {
this._aa = value.replace(/\D/g, '');
}
}
}Previous: About closures, I don't understand.
Next: Vue does a search and asks for it every time he presses the keyboard.
in router.js, because the breadcrumb component is used in multiple pages, the breadcrumb component is referenced by nested named views: { path: Manage , name: , component: function(res) { require([ .. components common layo...
wrote an H5 page. According to the official description of Wechat jssdk, it is found that the shared icons and descriptions are invalid. the code is like this ....
In the vue-cli project, I directly introduced the particls library into index.html, and the related files are placed in the static directory . <div id="particles-js">< div> <script type="text javascript" src="s...
the data received on the server is [{ "name ": "TOM ", "age ": "16 "}, { "name ": "JACK ", "age ": "18 "}, { "name ": "marry ", "age ": "20 "}] I think there is something wrong with the loop code in html. <ul v-for="item in items"...
how to connect vue1.0 to the domed components generated by qdQQ, is invalid when index.html introduces js, and clicks on the dom node, and cannot afford to call qq ...
create filter.js in the js folder in src assets main ...
< div vFFOR = "list in item " > < span VFF bindcharacters list.user.name > list.user.name outputs the name "Xiao Hong " in the view. However, the console will report that name does not define < div > those who are familiar with angular...
as shown in the red box of the second picture, is there any recommendation for this plug-in? Thank you. the screenshot is uploaded, so let s just look at it. nothing can be found in vueawesome. ...
version: "version ": "1.1.4 ", problem description: in the table header, if you want to add the Tooltip component, if the Tooltip component does not use the slot slot, it will display normally, but when the content to be displayed is too much, using ...
just can t show it. Thank you very much for your advice. ...
Front-end Xiaobai, a company internship, needs to export all the data in the paging to the excel table. After finding the answers, you only finish exporting the data on the current page. I would like to ask how to export the data of all pages. I tried t...
use axios for registration, use graphic verification code to verify whether it is correct, cannot be verified correctly, 1. Get the graphic verification code first this.$http({ method: get , url: this.api + app platform getImgCo...
the demand has changed. Previously, you only need to submit the id array of the selected leaf node, and then you can get it directly through the official api [getCheckedKeys]. Now it is required to also pass the id of the parent node. get stuck. Many ...
as shown in the figure, I used the menu bar component of ivew in vue figure 1. I selected the content on the right side of the login log to display the contents of the login log, which is normal . then I set up a @ click route on the account profile d...
< H2 > now there is a strange situation, that is, when I use the Loadmore component, the pull-up load is not performed, only the drop-down refresh is performed. It only executes every time I change the location of the component, but after I refresh it, i...
localhost:8080 -sharp register ; register(); :localhost:8080 ?-sharp register;ajax;;localhost:8080 ?-sharp register;home : vue@;formform ...
In vue, when the account input and password input of the login page communicate between two different components, how to verify the login through axios? do you need to create a new login interface at this time? ...
I make a login interface using tabs in elementui to divide student login and teacher login <el-tabs v-model="activeName" @tab-click="handleClick"> <el-tab-pane label="" name="first"> <tabs>...
vue , pug , VaForminput , dom ...
manually adding window.onerror in 2.5 does not catch errors or how does it work? Does have to be handled in Vue.config.errorHandler ? ...