With the continuous development of mobile Internet, small programs are getting more and more attention and love from people. The uniapp framework has been favored by the majority of developers for its advantages of cross-platform, one-time development of multiple terminals, and ease of use. However, during development, we will inevitably encounter some problems. For example, I modified the style in uniapp but found that it did not take effect in the mini program. So how to solve this problem? Let’s discuss the causes and solutions to this problem.
When modifying the style in uniapp, the style is usually written in the style
tag. However, sometimes we find that we cannot see style changes in the mini program, such as modifying properties such as color, font size, etc., but they are displayed normally during preview. Why is this? There are several possible reasons:
Sometimes we put the style of the WXML element in an external style sheet, such as in Some common styles are defined in app.wxss
, and then used in a component. At this time, if we accidentally write the wrong path to the style file, the style will not take effect.
In uniapp, in order to avoid styles from interfering with each other, we can use the scoped
attribute to limit the scope. But if we abuse the scoped
attribute and add this attribute to all styles, it may cause the style to become invalid.
In CSS, different style selectors have different priorities. Some selectors have higher priority and some have lower priority. If we modify a low-priority style but it is overwritten by a high-priority style, the style will not take effect.
Mini programs have their own caching mechanism. Sometimes the style is modified and the cache needs to be cleared to see the effect. If the cache is not cleared, the style will not take effect.
In response to the above problem, we can take the following methods to solve the problem of the style not taking effect:
If our style leaves the external style sheet path, the style will not take effect. So we need to double check whether the path to the style file is correct.
When using the scoped
attribute, we must be careful not to abuse it, only where we need to limit the scope. Add this attribute. If you don't need to limit the scope, don't add this attribute.
If the priority of the style selector is incorrect, the style will be overwritten. We can solve this problem by changing the priority of the selector. You can use !important
to increase the style priority, or use more specific selectors for decoration.
If we have modified the style, but it still does not take effect, it may be because the mini program has cached the style. At this time, we can clear the cache in the background of the mini program, or add some random numbers to the code to break the cache to update the style.
Through the above introduction, we can see that the problem of modifying the style applet in uniapp not taking effect may be caused by a variety of reasons. During the development process, we need to carefully check the attributes and selectors of each style to ensure that no errors occur. At the same time, you also need to understand the caching mechanism of the mini program and clear the cache in time. I hope this article can help everyone solve style problems during development and make the development of uniapp smoother.
The above is the detailed content of uniapp style modification applet does not take effect. For more information, please follow other related articles on the PHP Chinese website!