3 ms·
The weird thing is that there's other teams within Google who offer autocomplete libraries that simply don't work because Chrome overlays it's own autocomplete
by andrewstuart 7y ago
The weird thing is that there's other teams within Google who offer autocomplete libraries that simply don't work because Chrome overlays it's own autocomplete on top.
The maps team seems to have given up on trying to resolve that.
Chrome team have made a judgement that autocomplete is required and no-one - not even other teams within Google are allowed to override that functionality.
It's weird.
- jefftk 7y ago> not even other teams within Google are allowed to override that functionality Isn't that how things should work? If other teams within Google had a special way to override autocomplete wouldn't that be worse? (Disclosure: I work at Google)
- andrewstuart 7y agoMy point is that this decision from the Chrome team even breaks Google's own software. This emphasises the craziness of the unilateral decision by the Chrome team which is essentially saying: "we, the Chrome team are correct and everyone else can go jump in the lake". I'm not suggesting that Google should have secret special ways to do things.
- atomicfiredoll 7y agoAngular Material's Autocomplete component is an example of this. Our users would have found that really helpful... if Chrome's autofill behavior didn't break it.
- nikanj 7y agoGoogle really is the new Microsoft
- sixothree 7y agoIn spirit maybe. But in practice it seems worse.