In bug 1341086, we add ThreadSafeTextIsOnlyWhitespace and ThreadSafeIsSignificantChild, which both do the same thing as their non-threadsafe counterparts, but if the whitespace info is not cached we will recalculate and discard the info. This is suboptimal, and it would be nice if Stylo could still cache this info, maybe after traversal is over. It should be possible to use the same framework that we plan to use in bug 1338982 (and bug 1345950)
status-firefox57=wontfix unless someone thinks this bug should block 57
status-firefox57: --- → wontfix
You need to log in before you can comment on or make changes to this bug.