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
That doesn't seem to be mentioned in readme, but the callback skips at least one frame after the element is inserted to DOM. So for example if there's initializer function for a rule, that adds some styles or content to an element that is added to DOM, the element still appears in DOM unstyled for a single frame, then the rule is hit. That creates FOUC.
I guess that can be prevented by hiding element for that frame in some way...
That is the case for spect. selector-observer doesn't have that issue.
The text was updated successfully, but these errors were encountered:
dy
changed the title
First frame after insertion
First frame after insertion FOUC
Mar 23, 2020
That doesn't seem to be mentioned in readme, but the callback skips at least one frame after the element is inserted to DOM. So for example if there's initializer function for a rule, that adds some styles or content to an element that is added to DOM, the element still appears in DOM unstyled for a single frame, then the rule is hit. That creates FOUC.
I guess that can be prevented by hiding element for that frame in some way...
That is the case for spect. selector-observer doesn't have that issue.
The text was updated successfully, but these errors were encountered: