←back to thread

Et Tu, Grammarly?

(dbushell.com)
279 points dbushell | 4 comments | | HN request time: 0.797s | source
1. Aldipower ◴[] No.43515000[source]
I've a similiar problem with Google Translate that breaks my web app. Users, using Google Translate, complaining my app is broken, but it was Google changing the state of my app from a higher meta level. Really bad practice..

I am trying to detect Google Translate and print a warning then.

replies(2): >>43515029 #>>43516979 #
2. netsharc ◴[] No.43515029[source]
Maybe related, from 2 days ago: https://www.pewresearch.org/decoded/2025/03/21/how-a-glitch-... / https://news.ycombinator.com/item?id=43441880
3. MartijnHols ◴[] No.43516979[source]
While Google Translate's interference sucks, with current browser tools, I don't think they can really operate any other way.

This is mostly because of cases where they need to translate a sentence like "[Click here] for more information". When translating it to another language, they may have to move the link to the end e.g. "For more information, [click here]". The only way to achieve that is to shuffle DOM elements around, which can cause interference with interactive apps.

There's still a lot the Google Translate team can do to reduce the interference they cause, but I don't think they can fully eliminate it without some new browser APIs.

replies(1): >>43518847 #
4. kelvinjps10 ◴[] No.43518847[source]
But they are the owners of a browser