JS: Performance fix for chrome Holy performance killer batman! Chrome was updating nodelists on every change instead of batching them like firefox resulting in exponentially worse performance. (Like "This fix made it go from 40 minutes to 7 seconds" exponentially)
CSS: Set contain on kint dumps to help client side performance The contain and content-visibility properties are very new and can actually break rendering entirely in different circumstances for different browsers. For now we'll stick to good old display:none and just hope contain implementations get good enough to give us some perf down the line.
Parser::noRecurseCall: Simplify logic