@@ -154,7 +154,9 @@ <h4 id="MatButton" class="docs-header-link docs-api-h4 docs-api-class-name">
154154 </ td >
155155 < td class ="docs-api-property-description "> < p > Natively disabled buttons prevent focus and any pointer events from reaching the button.
156156In some scenarios this might not be desirable, because it can prevent users from finding out
157- why the button is disabled (e.g. via tooltip).</ p >
157+ why the button is disabled (e.g. via tooltip). This is also useful for buttons that may
158+ become disabled when activated, which would cause focus to be transferred to the document
159+ body instead of remaining on the button.</ p >
158160< p > Enabling this input will change the button so that it is styled to be disabled and will be
159161marked as < code > aria-disabled</ code > , but it will allow the button to receive events and focus.</ p >
160162< p > Note that by enabling this, you need to set the < code > tabindex</ code > yourself if the button isn't
@@ -354,7 +356,9 @@ <h4 id="MatFabButton" class="docs-header-link docs-api-h4 docs-api-class-name">
354356 </ td >
355357 < td class ="docs-api-property-description "> < p > Natively disabled buttons prevent focus and any pointer events from reaching the button.
356358In some scenarios this might not be desirable, because it can prevent users from finding out
357- why the button is disabled (e.g. via tooltip).</ p >
359+ why the button is disabled (e.g. via tooltip). This is also useful for buttons that may
360+ become disabled when activated, which would cause focus to be transferred to the document
361+ body instead of remaining on the button.</ p >
358362< p > Enabling this input will change the button so that it is styled to be disabled and will be
359363marked as < code > aria-disabled</ code > , but it will allow the button to receive events and focus.</ p >
360364< p > Note that by enabling this, you need to set the < code > tabindex</ code > yourself if the button isn't
@@ -531,7 +535,9 @@ <h4 id="MatMiniFabButton" class="docs-header-link docs-api-h4 docs-api-class-nam
531535 </ td >
532536 < td class ="docs-api-property-description "> < p > Natively disabled buttons prevent focus and any pointer events from reaching the button.
533537In some scenarios this might not be desirable, because it can prevent users from finding out
534- why the button is disabled (e.g. via tooltip).</ p >
538+ why the button is disabled (e.g. via tooltip). This is also useful for buttons that may
539+ become disabled when activated, which would cause focus to be transferred to the document
540+ body instead of remaining on the button.</ p >
535541< p > Enabling this input will change the button so that it is styled to be disabled and will be
536542marked as < code > aria-disabled</ code > , but it will allow the button to receive events and focus.</ p >
537543< p > Note that by enabling this, you need to set the < code > tabindex</ code > yourself if the button isn't
@@ -695,7 +701,9 @@ <h4 id="MatIconButton" class="docs-header-link docs-api-h4 docs-api-class-name">
695701 </ td >
696702 < td class ="docs-api-property-description "> < p > Natively disabled buttons prevent focus and any pointer events from reaching the button.
697703In some scenarios this might not be desirable, because it can prevent users from finding out
698- why the button is disabled (e.g. via tooltip).</ p >
704+ why the button is disabled (e.g. via tooltip). This is also useful for buttons that may
705+ become disabled when activated, which would cause focus to be transferred to the document
706+ body instead of remaining on the button.</ p >
699707< p > Enabling this input will change the button so that it is styled to be disabled and will be
700708marked as < code > aria-disabled</ code > , but it will allow the button to receive events and focus.</ p >
701709< p > Note that by enabling this, you need to set the < code > tabindex</ code > yourself if the button isn't
0 commit comments