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

升级到2.7后,AutoComplete组件size属性失效。 #4766

Closed
lllyyylll2 opened this issue Feb 6, 2017 · 1 comment · Fixed by #4768
Closed

升级到2.7后,AutoComplete组件size属性失效。 #4766

lllyyylll2 opened this issue Feb 6, 2017 · 1 comment · Fixed by #4768
Assignees
Labels
🐛 Bug Ant Design Team had proved that this is a bug.

Comments

@lllyyylll2
Copy link

lllyyylll2 commented Feb 6, 2017

Environment(required)

  • antd version: 2.7.1
  • OS and its version: WINDOW 10
  • Browser and its version: Chrome 55.0.2883.87 m (64-bit)

What did you do? Please provide steps to re-produce your problem.

<AutoComplete size="large" />

What do you expected?

large size AutoComplete

What happen?

didn't work

Re-producible online demo

http://codepen.io/anon/pen/xgzBKe

@ddcat1115 ddcat1115 added the 🐛 Bug Ant Design Team had proved that this is a bug. label Feb 6, 2017
@RaoHai RaoHai self-assigned this Feb 6, 2017
RaoHai added a commit to RaoHai/ant-design that referenced this issue Feb 6, 2017
ddcat1115 pushed a commit that referenced this issue Feb 9, 2017
*  fix AutoComplete size

 + close #4766

* use input mixin

* use css variables

*  use children directly instead of React.Children.toArray

 + close #4778
@lock
Copy link

lock bot commented May 2, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators May 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐛 Bug Ant Design Team had proved that this is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants