[Forrest]

The answer is in the article you cited:
The bug seems to have been introduced into WebKit at some point just before Omni grabbed a copy to build OmniWeb 5.5 on.

The scope of the bug is beyond me. I have verified it’s fixed in the latest WebKit nightly and thus when OmniWeb updates it’s copy with 5.5.1 the issue should be resolved.