Open in StackBlitz

pnpm add https://pkg.pr.new/element-plus/element-plus@23053

npm i https://pkg.pr.new/element-plus/element-plus@23053

yarn add https://pkg.pr.new/element-plus/[email protected]

commit: 5ff86e4

🧪 Playground Preview: https://element-plus.run/?pr=23053
Please comment the example via this playground if needed.

Before

After

We can refer to other components and add teleported and append-to props. for example https://element-plus.org/en-US/component/select

We can refer to other components and add teleported and append-to props. for example https://element-plus.org/en-US/component/select

Thanks for your suggestions. I've fixed it.

The latest Playground Case

Thanks for your contribution! I have a suggestion.

Thanks.

@micaiguai Thanks for your contribution! ❤️

Sir, may I ask, when the affix component is activated and switches between fixed and non-fixed states, it will trigger the unloading and re-mounting of the component. I noticed in the code of Element-plus that teleported has encapsulated an additional layer and uses v-if for switching. In fact, teleported has a disabled attribute for switching purposes. When using the affix component for fixed business with state, the state switching triggers the component's lifecycle again. Perhaps this is not what I expected. I would like to ask if there are any other considerations behind this design of teleported?

Sir, may I ask, when the affix component is activated and switches between fixed and non-fixed states, it will trigger the unloading and re-mounting of the component. I noticed in the code of Element-plus that teleported has encapsulated an additional layer and uses v-if for switching. In fact, teleported has a disabled attribute for switching purposes. When using the affix component for fixed business with state, the state switching triggers the component's lifecycle again. Perhaps this is not what I expected. I would like to ask if there are any other considerations behind this design of teleported?

Thanks for pointing this out! I've solved this problem.

Related: #23219 (comment)

Thank you very much, but I have encountered another issue. When scaling the screen with the push pin fixed, the width and height of the push pin will not change with the screen scaling, resulting in a horizontal scrollbar. Boss, can you help me take a look at this problem