3 ms·
It was a bug in WebKit that WebKit had to fix (and as you know, Safari takes a long time getting those fixes into consumer's hands).
by concinds 1y ago
It was a bug in WebKit that WebKit had to fix (and as you know, Safari takes a long time getting those fixes into consumer's hands).
- mmis1000 1y ago> takes a long time If it even does.
- Klonoar 1y agoBoth those sites existed - either in practice or in concept - for well over a decade now. If the giant mega corporation behind those products is blaming WebKit, maybe they should instead devote some engineering resources to just work around the bug. Testing in non-Chrome browsers should identify anything like this before stuff ships. It is legitimately not hard to do.