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

[DropDownMenu] Typeahead #18

Closed
mschipperheyn opened this issue Nov 9, 2014 · 8 comments
Closed

[DropDownMenu] Typeahead #18

mschipperheyn opened this issue Nov 9, 2014 · 8 comments
Labels
new feature New feature or request

Comments

@mschipperheyn
Copy link

Very nice! Would love to see type ahead functionality, which consists AFAIC of three elements.

  • typeahead
  • typeahead tag selection
  • typeahead within textarea (@Friend names)
@hai-cea
Copy link
Member

hai-cea commented Nov 11, 2014

Yes :) Although, I think there are some other basic components we'd like to implement first.

@akinnee
Copy link

akinnee commented Feb 3, 2015

+1 for typeahead dropdown menu

@ezequiel
Copy link

We recently released a React Typeahead/Autocomplete component. It's well tested, and used in production by Yahoo Mail. It can be found here: https://github.com/ezequiel/react-typeahead-component. It would be great to get these two projects working together. :)

@hai-cea hai-cea changed the title Typeahead [DropDownMenu] Typeahead Jun 18, 2015
@cgestes
Copy link
Contributor

cgestes commented Jul 2, 2015

I started to look at it. (will focus on typeahead in a textarea first)

@piyushchauhan2011
Copy link

👍

@newoga
Copy link
Contributor

newoga commented Dec 2, 2015

FYI Some of this was solved by #1985. However, we still need TypeAhead/AutoComplete for tag completion and within TextArea :)

@newoga
Copy link
Contributor

newoga commented Dec 2, 2015

Also, I think it would nice to use AutoComplete/TypeAhead with a Chips component. #1119 #2214
https://www.google.com/design/spec/components/chips.html#

@tahir-masood1
Copy link

+1 for typeahead within textarea

mnajdova referenced this issue in mnajdova/material-ui Nov 10, 2020
Move picker sources into lab (#4)

Update README.md

[DatePicker] Refactor pickers tests to testing-library and mocha (#5)

[TimePicker] Migrate tests to testing library (#8)

[DateTimePicker] Migrate tests  (#9)

Fix all pickers linter errors (#10)

Fix all circular dependencies (#11)

* Fix all circular dependencies

* Enable mocha eslint rules for typescript tests

[test] The last step to a green CI (#15)

Migrate pickers docs (#12)

Downgrade to withStyles for pickers sources (#16)

Add public api exports for pickers components (#17)

Consolidate component namespace and theme augmentation  (#18)

Describe conformance for pickers sub-components (#19)

Autogenerate proptypes for typescript sources  (#20)

Proper build output (#21)

Clear migration artifacts  (#23)

Eslint rule for lower-case test name convention  (#24)

DateRangePicker  (#25)

yarn deduplicate

Remove GridListTile

[DateTimePicker] Fix migration unit tests

Fix types

Fix typescript types migration issues

Fix yarn lerna build (#33)

Fix karma tests

use window.Touch for CI karma tests

Remove more outdated diff noise (#34)

Replace not valid formats with valid ISO strings

Try to fix CI touch tests

Skip tests if Touch events are not supported

Fix merge conflicts

Actually type-check

Fix safari tests

Remove lowercase test name rule

The casing is up to the test author.
We're not the grammar police in tests.

Fix lint

Format

Remove overzealous eslint-disable*

Debug failing tests

Better debugging

Timezones are fun

was isoString th efix?

Let's find out what's failing and then skip it

Branch for safari

Skip DateRangePicker in browsers

review

Matt's review

Co-authored-by: Matt <github@nospam.33m.co>

format

docs:i18n
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature or request
Projects
None yet
Development

No branches or pull requests

10 participants