It could easily happen client-side, with something like /Chrome/.test(navigator.userAgent). I mean, there's probably sites using code like this already, why el

It could easily happen client-side, with something like /Chrome/.test(navigator.userAgent). I mean, there's probably sites using code like this already, why else would IE implement such a user-agent? But then they can't really know which Chrome feature the code is looking for. I guess they are moving from being unfairly excluded from modern standards, to possibly overshooting their target and getting served experimental features they don't support.