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 Jul 30, 2018. It is now read-only.
Enhancement
Currently, the deferred properties function call is made on the next animation frame unless the projector is set to sync and there is no indication of wether if the function has been called on before or after the dom has been updated.
Moving deferred properties to same animation frame in all cases and adding a flag to denote if it's the first or second call will make it easier / possible to perform the class based domnode calculations required for more complicated ui transitions / animations.
For example:
protectedrender(){letwidth='';returnv('div',(inserted,deferred)=>{constexpandedAndUpdated=deferred&&this._expanded;if(expandedAndUpdated){// previously we would not have been able to do this in the same AFconstdimensions=this.meta(Dimensions).get('root');width=dimensions.size.width;}return{key: 'root',classes: [this._expanded ? css.expanded : null]};},[width]);}
The text was updated successfully, but these errors were encountered:
Enhancement
Currently, the deferred properties function call is made on the next animation frame unless the projector is set to
sync
and there is no indication of wether if the function has been called on before or after the dom has been updated.Moving deferred properties to same animation frame in all cases and adding a flag to denote if it's the first or second call will make it easier / possible to perform the class based domnode calculations required for more complicated ui transitions / animations.
For example:
The text was updated successfully, but these errors were encountered: