An error appeared on Google that crashed the site!

Google’s online document creator and editor platform Google Docsis facing a notable error. This error, which causes the developers to argue with each other, is the same word. 5 times appears by writing.

After detecting this surprising error, writing a common word, crash the software shows that it may be sufficient. With the statement shared the other day, the error is seen in all accounts and browsers.


Google did not allow inappropriate ads!

According to the 2021 Ad Security Report data published by Google, the company removed 3.4 billion inappropriate ads in 2021.

Site crashed after repeatedly typing ‘And’ in Docs

Google Docs user Pat NeedhamAccording to a statement given to Google, in Google Docs “And. And. And. And. Andean” The Docs tab in the browser crashes when you type. The error affected Documents in personal, G Suite Basic, and work accounts. Besides, the same problem Firefox and Chrome Turns out it’s in their browser as well.

https://i0.wp.com/shiftdelete.net/wp-content/uploads/2022/05/Googleda-site-cokerten-bir-hata-ortaya-cikti-2.jpg?resize=1170%2C658&ssl=1

After this question, many people wondered if the same error occurred in different words. According to the shares made by users, ‘anyway‘, Who‘,’Therefore,‘,’thigh‘,’Why‘ and ‘besides‘ also caused Docs to crash.

After all this, a Google employee made a statement about the error. In the employee statement, “Dear Google Docs users, we are aware of the issue and are currently working on a fix. Thank you for uncovering this issue and sharing it with us. We will keep you informed.” said.

https://i0.wp.com/shiftdelete.net/wp-content/uploads/2022/05/Googleda-site-cokerten-bir-hata-ortaya-cikti.jpg?resize=1170%2C658&ssl=1

This has come after the introduction of the ‘assisted writing’ feature, which allows Google Docs users to improve the quality of their writing. Although there is no clear explanation about whether the problem has been resolved or not, there is no error for now.

So, what do you think about this error? Do not forget to share your views with us in the comments section or on the SDN Forum.

source site-32