Comment by jraph

Apparently it's a workaround until https://bugs.webkit.org/show_bug.cgi?id=275223 is understood and fixed.

Seems more reasonable than how it looked at first.