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
Ability to display tooltip on disabled button / element #7953
Comments
see #5040 |
@ghd8 thanks. Disappointing. |
dszidi
pushed a commit
to truenas/webui
that referenced
this issue
Feb 19, 2018
…d. Unable to add tooltip with warning message due to this issue. angular/components#7953
denis-yuen
added a commit
to dockstore/dockstore-ui2
that referenced
this issue
Aug 28, 2018
* would prefer tooltip, but for angular/components#7953
denis-yuen
added a commit
to dockstore/dockstore-ui2
that referenced
this issue
Aug 30, 2018
* Hide disabled option altogether * would prefer tooltip, but for angular/components#7953 * PR changes
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
feature (maybe bug)
What is the expected behavior?
Ability to display tooltip on disabled button / element.
e.g.
or
What is the current behavior?
Both tooltip and button are disabled using
disabled
input attribute. In order to just disable one or the other, you must use a helper element to split the component up.e.g.
What are the steps to reproduce?
See https://stackblitz.com/edit/angular-material2-issue
In the above, the both the button and the tooltip are disabled.
What is the use-case or motivation for changing an existing behavior?
Ability to just disable a
button
/ form element & not disable its associatedtooltip
, or vice-versa. E.g. this is useful if you'd like the tooltip to explain why the button is disabled.Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular: 4.4.6
material: 2.0.0-beta.12
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: