No action taken since it was a page-specific issue. However, it's possible that the recent 2017 revisions to CSS would have fixed this anyway. Maybe.
No action taken since it was a page-specific issue. However, it's possible that the recent 2017 revisions to CSS would have fixed this anyway. Maybe.