Maybe foe the next release?
The error:
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.Unscored
Top function call
Total reflow time
…site/cs-classic.7.8.8.js?ver=7.8.8:2:36526(ohlalab.com.mx)
What’s causing the forced reflow
Forced reflow happens when JS reads layout properties ( offsetWidth , offsetHeight , getBoundingClientRect ) immediately after writing to the DOM/styles, forcing the browser to recalculate layout mid-script. The file has three main offenders :
1. getOuterHeight function (likely near character 36526):
// Writes styles...t.style.display = "block"t.style.position = "absolute"t.style.visibility = "hidden"// Then immediately reads layout → FORCED REFLOWMath.max(0, e, t.scrollHeight, t.offsetHeight)
2. inner-wrap behavior:
r.append(i)i.offsetHeight // reads layout right after DOM mutation → FORCED REFLOW
(This is intentional — it flushes styles before removing a class to trigger CSS transitions.)
3. lockMotion function:
t.style.setProperty("transition", "none", "important")t.offsetHeight // intentional flush to force style recalc
the getOuterHeight / inner-wrap functions are the culprits. The fix needs to come from them by batching DOM reads before writes.