The use of vue cache routing components

When we switch from one component to another, the routing component that has not been displayed remains mounted and not destroyed. When we switch back, the previous data is still maintained, for example, entering data in a text box, Then switch to another page, and then switch to the previous text box interface, the data of the text box is still saved. The web page experience will be better.

The usage method is as follows: use the <keep-alive> tag, which can also use include attribute: string or regular expression, only matching components will be cached, exclude attribute: string or regular expression, any successful matching component will be Will not be cached, used more.
<keep-alive :include="['AAA','BBB']">
<router-view></router-view>
</keep-alive>

Comments

cli.isMultipleCompiler is not a function

An error is reported when using webpack-dev-server to build a development server, and the error message is as follows:[webpack-cli] TypeError: cli.isMultipleCompiler is not a function.

What is the difference between width property 100% and auto in css?

width:auto: The default width value of block-level elements. When set to this value, the browser will automatically select an appropriate width value to adapt to the width of the parent element. When the width is set to 100%, the width of the child element box The value is equal to the parent's content, and as the parent's content automatically changes, after adding the padding and margin of the child element, its width remains unchanged, which is the difference from setting it to auto. But we most often use width:auto, because it is more flexible, width:100% is used less, because when adding padding or margin, this method is easy to make it exceed the parent box and destroy the original layout.

Access to XMLHttpRequest at 'http://localhost:8080/xxx' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Due to browser same-origin policy restrictions. The Same Origin Policy is a convention. This is the main and essential security feature of the browser. Without the same-origin policy, normal browser functionality may be affected. The web is built on the same-origin policy, and browsers are just one implementation of the same-origin policy. The Same Origin Policy prevents JavaScript scripts from one domain from interacting with content from another domain. The so-called same origin (that is, the same domain) means that two pages have the same protocol, host and port.

code sky

Search This Blog