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.

Sign up for GitHub

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

Jump to bottom

[AvatarButton] New component suggestion #1038

Closed
CumpsD opened this issue Jul 4, 2015 · 3 comments
Closed

[AvatarButton] New component suggestion #1038

CumpsD opened this issue Jul 4, 2015 · 3 comments
Labels
new feature New feature or request out of scope The problem looks valid but we won't fix it (maybe we will revisit it in the future)

Comments

@CumpsD
Copy link
Contributor

CumpsD commented Jul 4, 2015

As suggested in #836 (comment) it would be interesting to have a new component called AvatarButton which is a mix between an Avatar and a RaisedButton, so that we can have image avatars with hover over + ripple effects.
@shaurya947 shaurya947 added the new feature New feature or request label Nov 17, 2015
@alitaheri alitaheri added New Component Request and removed new feature New feature or request labels Dec 8, 2015
@SukantGujar
Copy link

I created a similar issue. Instead of a new component, IconButton should support Avatars.

@mbrookes
Copy link
Member

Ref: #2913

@oliviertassinari oliviertassinari added new feature New feature or request v1-alpha and removed New Component labels Jun 23, 2017
@oliviertassinari
Copy link
Member

We have been exposing the underlying building block of our button components: ButtonBase #7727. I can be used to build such AvatarButton on userland. I don't think that we need it in the core of the library.

@oliviertassinari oliviertassinari added the out of scope The problem looks valid but we won't fix it (maybe we will revisit it in the future) label Aug 22, 2017
mnajdova pushed a commit to mnajdova/material-ui that referenced this issue Nov 10, 2020
@neeschit @dmtrKovalenko
Use wildcard import rather than default import (mui#1038)
b21bbf1
mnajdova pushed a commit to mnajdova/material-ui that referenced this issue Nov 10, 2020
@dmtrKovalenko
Views refactoring (mui#1044)
689a36b 
* Created base <Picker /> component for rendering all possible views

* Recreate TimePicker with new <Picker /> component

* Add TimePicker toolbar and fully replace old TimePickerRoot

* Fix not generating docs when exported several components

* Redo DatePicker on <Picker />

* Grand Views Refactoring

* Fix Root-Pickers tests

* Fix ts errors

* Fix Object(...) is not a function error

* Fix loosing selected meridiem

* Use wildcard import rather than default import (mui#1038)

* [mui#1031] Fix className of ClockNumber selected state (mui#1045)

* Bugfix/spread input props (mui#1046)

* [mui#1031] Fix className of ClockNumber selected state

* [mui#1039] Fix not passing down InputProps

* Make InputProps not required

* Redo DateTimePickerToolbar to use grid

* Get rid of 'selected' and 'disabled' classes

* Fix console warnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new feature New feature or request out of scope The problem looks valid but we won't fix it (maybe we will revisit it in the future)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mbrookes @CumpsD @oliviertassinari @shaurya947 @SukantGujar @alitaheri