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 May 22, 2019. It is now read-only.
In the process of debugging a custom theme, I discovered that including a CSS file longer than 100 lines causes the entire renderer to go black and display nothing / take no input.
Does not seem to be tied to size, number of CSS selectors, or selector complexity, but purely line count.
Is this intentional?
Assuming that it is not intentional, some useful info:
Works as expected when CSS is split into seperate 100 line files, Possible File IO issue?
Does not appear to affect the JS, tested up to 1000 lines as still functional.
Breaks renderer regardless of location, if loaded after all content has already rendered it will still cause the entire DOM to turn black and go unresponsive.
The text was updated successfully, but these errors were encountered:
Possibly related to #46
In the process of debugging a custom theme, I discovered that including a CSS file longer than 100 lines causes the entire renderer to go black and display nothing / take no input.
Does not seem to be tied to size, number of CSS selectors, or selector complexity, but purely line count.
Is this intentional?
Assuming that it is not intentional, some useful info:
The text was updated successfully, but these errors were encountered: