Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can the drop-down box elements of the [Feature Request] Select component be configured to be generated into a select element or a sibling directory? #7468

Closed
mirari opened this issue Oct 13, 2017 · 5 comments

Comments

@mirari
Copy link

mirari commented Oct 13, 2017

Existing Component

Component Name

Select

Description

使用全屏API将指定元素设置为全屏后,其内部的select组件在点击后本应弹出的下拉框无法被看到。
因为el-select-dropdown元素并非位于全屏元素内部,而是body的子节点。
而Dialog组件都是可以保持自身位置在声明时所在的元素下的,没有这个问题。
希望select和message组件都可以增加一个配置项,用于指定el-select-dropdown或el-message-box__wrapper弹出时是挂载到body下还是select父元素或者是自行指定元素。

@element-bot element-bot changed the title [Feature Request] Select组件的下拉框元素能否可配置成生成到select元素下或同级目录? Can the drop-down box elements of the [Feature Request] Select component be configured to be generated into a select element or a sibling directory? Oct 13, 2017
@element-bot
Copy link
Member

Translation of this issue:

Existing Component

yes

Component Name

Select

Description

After using the full screen API to set the specified element to full screen, the internal select component should not be seen after clicking the drop-down box that should have popped.

Because the el-select-dropdown element is not located inside the full screen element, it is the child node of the body.
And Dialog components can keep their position under the declaration of the elements, without this problem.

It is hoped that both select and message components can add a configuration item to specify whether el-select-dropdown or el-message-box__wrapper pops up to body or select parent element or self specified element when it pops up.

@wacky6
Copy link
Contributor

wacky6 commented Oct 13, 2017

Can you provide a demo?

@mirari
Copy link
Author

mirari commented Oct 16, 2017

@wacky6
Copy link
Contributor

wacky6 commented Oct 16, 2017

@Leopoldthecoder

@Leopoldthecoder
Copy link
Contributor

I'll look into it later this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants