Boris informs me that the bug in Safari that caused a blunder-render of this page has vanished with a new update. Good for them!