Element: [Bug Report] Select with filtering cannot be closed from caret

Created on 10 Oct 2019  ·  5Comments  ·  Source: ElemeFE/element

Element UI version

2.12.0

OS/Browsers version

Firefox 69.0.1 & Chrome 77.0.3865.90

Vue version

2.5.21

Reproduction Link

https://jsfiddle.net/ujqzL47h/6/

Steps to reproduce

  1. Open select list from caret icon.
  2. Try closing the list by clicking the icon again.

What is Expected?

Clicking on the close icon should close the select list.

What is actually happening?

Select list stays open and user has to click outside of the element to close the list.

However if you open the select list by clicking on the "el-input__inner" part of the element and press the close icon it works.

All 5 comments

blur:function(e){
let that=this,val="";
this.options.forEach(function(item){
if(that.Select==item.value){
that.Select="";
val=item.value;
}
})
this.Select=val;
}
加个blur事件,亲测有效

Sorry. Where do you mean that adding a blur would help? I think that this is bug in the select component.

blur event,not a bug

------------------ 原始邮件 ------------------
发件人: "Pentti Laitinen"notifications@github.com;
发送时间: 2019年10月11日(星期五) 中午1:55
收件人: "ElemeFE/element"element@noreply.github.com;
抄送: "阿蒙"1078619622@qq.com;"Comment"comment@noreply.github.com;
主题: Re: [ElemeFE/element] [Bug Report] Select with filtering cannot beclosed from caret (#17668)

Sorry. Where do you mean adding blur would help? I think that this is bug in the select component.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Here you can see the demonstration of the bug.

opening-from-caret-breaks-closing

You can try what I added,blur event

------------------ 原始邮件 ------------------
发件人: "Pentti Laitinen"notifications@github.com;
发送时间: 2019年10月11日(星期五) 下午2:23
收件人: "ElemeFE/element"element@noreply.github.com;
抄送: "阿蒙"1078619622@qq.com;"Comment"comment@noreply.github.com;
主题: Re: [ElemeFE/element] [Bug Report] Select with filtering cannot beclosed from caret (#17668)

Here you can see the demonstration of the bug.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Was this page helpful?
0 / 5 - 0 ratings