I have also encountered this problem, because the rem unit used has a decimal point. Changing it to an integer px will make it less ambiguous The specific reason may be a problem with the browser’s css3 animation rendering process. Stay tuned and wait for the expert’s answer
Relevant information on the Internet says that it is because the 3D animation uses a decimal point setting, which causes the calculated px value to appear as a non-integer, resulting in blurry and unclear problems, but the specific reason is not yet determined. In addition, some 3D animations that need to be used can only set decimal multiples or percentage multiples. The calculated results cannot be completely guaranteed to be integers, so this direction may not be able to completely solve the problem.
http://www.cnblogs.com/rubylo...
I have also encountered this problem, because the
rem
unit used has a decimal point. Changing it to an integerpx
will make it less ambiguousThe specific reason may be a problem with the browser’s css3 animation rendering process. Stay tuned and wait for the expert’s answer
Relevant information on the Internet says that it is because the 3D animation uses a decimal point setting, which causes the calculated px value to appear as a non-integer, resulting in blurry and unclear problems, but the specific reason is not yet determined. In addition, some 3D animations that need to be used can only set decimal multiples or percentage multiples. The calculated results cannot be completely guaranteed to be integers, so this direction may not be able to completely solve the problem.