Spin-off of  issue 448427 . The fix supported it for same-origin favicons, but not yet cross-origin ones. By the specification, cross-origin ones should also be supported but it's likely a less important use case.