Question and answer for yourself: The premise is that you cannot use the header component that comes with weex
Mainly through the common events provided by weex, appear and disappear, plus the control switch By default, the element is in the document flow. When the element disappears from the screen when scrolling, use the disappear event and give it fixed. When scrolling to this element and appearing on the screen again, use the appear event and remove fixed
This method can solve the above problems, but there is still a small flaw, that is, it must be scrolled until the element disappears from the screen before it can be fixed. Unlike ordinary DOM operations, it is fixed as soon as the target element is touched
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Question and answer for yourself:
The premise is that you cannot use the header component that comes with weex
Mainly through the common events provided by weex, appear and disappear, plus the control switch
By default, the element is in the document flow. When the element disappears from the screen when scrolling, use the disappear event and give it fixed.
When scrolling to this element and appearing on the screen again, use the appear event and remove fixed
This method can solve the above problems, but there is still a small flaw, that is, it must be scrolled until the element disappears from the screen before it can be fixed. Unlike ordinary DOM operations, it is fixed as soon as the target element is touched
I just came into contact with weex and found that the mobile playground scanning page is blank.