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
With sufficiently large stylesheets, there is a noticeable flicker when loading the sheet; after the HTML renders, but before the CSS is applied. Angular and uiRouter both have solutions for this issue, but angular-css doesn't support either of them natively.
ngCloak does wait until the HTML renders, but the stylesheet lags behind considerably; and I can't find a way to use angular-css inside ui-router's resolve. Support for either of these would be fantastic. Personally, I think the ngCloak approach is more "Angular", but there needs to be a way to wait for the stylesheet before showing the page.
Thank you so much for an otherwise amazing project! This feels like one of those things that are so obvious it's weird they're not built into Angular as it is. Keep up the good work! 😁
The text was updated successfully, but these errors were encountered:
One simple fix without touching any of the code is something like this: http://stackoverflow.com/a/21297361, basically you apply a display:none class to the part of the html you'd like to cloak, then uncloak it in your dynamically loaded css.
With sufficiently large stylesheets, there is a noticeable flicker when loading the sheet; after the HTML renders, but before the CSS is applied. Angular and uiRouter both have solutions for this issue, but
angular-css
doesn't support either of them natively.ngCloak
does wait until the HTML renders, but the stylesheet lags behind considerably; and I can't find a way to useangular-css
inside ui-router'sresolve
. Support for either of these would be fantastic. Personally, I think thengCloak
approach is more "Angular", but there needs to be a way to wait for the stylesheet before showing the page.Thank you so much for an otherwise amazing project! This feels like one of those things that are so obvious it's weird they're not built into Angular as it is. Keep up the good work! 😁
The text was updated successfully, but these errors were encountered: