You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
Currently, there is often a requirement that the Speed Dial's parent use ng-cloak. Although we document this, it should not be required.
The main reason this is currently necessary is because the Speed Dial uses flex positioning for the hidden items, meaning that the "default" CSS state of the component has the items positioned where they will be when opened, and we use JS to translate the positions to be hidden behind the trigger.
Ideally, we would ensure that the component starts out closed with all of the items hidden behind the FAB and upon opening, it translates the items into place. This may require a rewrite of the layout/CSS to use absolute/relative positioning rather than flex.
The text was updated successfully, but these errors were encountered:
Currently, there is often a requirement that the Speed Dial's parent use
ng-cloak
. Although we document this, it should not be required.The main reason this is currently necessary is because the Speed Dial uses flex positioning for the hidden items, meaning that the "default" CSS state of the component has the items positioned where they will be when opened, and we use JS to translate the positions to be hidden behind the trigger.
Ideally, we would ensure that the component starts out closed with all of the items hidden behind the FAB and upon opening, it translates the items into place. This may require a rewrite of the layout/CSS to use absolute/relative positioning rather than flex.
The text was updated successfully, but these errors were encountered: