You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change region to Arabic region (QA for example) (do this at bottom right Settings -> Search Settings)
Change language to Arabic (this is important, English Google is fine)
Search anything
Watch the page reload forever
I have no idea what is causing this, highly highly likely it is on Google's end and not ours but we still need to know what is causing this.
The only solution is to whitelist or turn off Wudooh, delaying the update still breaks it.
I am curious if Google can actually detect the update function changing stuff on the page and doesn't like it and causes a refresh maybe as a security thing or something as many garbage extensions will actuall insert ads into Google search results even if you have adblock on (seen this firsthand). This is troubling but I'll need to explore further, if it really is the case then we need to change to an update by changing styling method and not update by adding Nodes or HTMLElements.
Look at #7 again because we explored the advantages and issues of such a method, mainly when a HTMLElement has both text to be updated (Arabic) and text to be ignored within it. The best looking way is the current, make a new HTMLElement for the text to be updated and set its styling but the ignored text remains the same. Thus the non-Arabic text is identical and only the Arabic text appears differently.
Absolute worst case, we make a switch for both methods with users changing methods as they wish and we ship an optimal list of them. This means adding a new element to the database. But this would technically kind of fix #7 but not in the ideal way but would also significantly complicate the extension as users now have to understand how the extension works. Inconvenient, but again what's worse is that it's all not ideal, it's just a fix but not a solution.
While I hate having to accomodate for other site's weird behaviors, in this case I don't mind as much because I know the reason Google are doing this and I completely understand it and kind of support it if I am correct.
Extension is free but now our thousands of users have to see shitty ads on their Google search results (which Google themselves have no idea about) which we'll make (probably illegal and definitely unethical) money from. Imagine how far this could go, and all from a shitty extension that downloads videos or does YouTube analytics or whatever in which case...
Fuck you you filthy capitalist human garbage dirty cunt companies who make things worse for everyone for a quick (and small) buck.
Indeed, money is the root of all evil.
The text was updated successfully, but these errors were encountered:
Replicate by:
I have no idea what is causing this, highly highly likely it is on Google's end and not ours but we still need to know what is causing this.
The only solution is to whitelist or turn off Wudooh, delaying the update still breaks it.
I am curious if Google can actually detect the update function changing stuff on the page and doesn't like it and causes a refresh maybe as a security thing or something as many garbage extensions will actuall insert ads into Google search results even if you have adblock on (seen this firsthand). This is troubling but I'll need to explore further, if it really is the case then we need to change to an update by changing styling method and not update by adding
Node
s orHTMLElement
s.Look at #7 again because we explored the advantages and issues of such a method, mainly when a
HTMLElement
has both text to be updated (Arabic) and text to be ignored within it. The best looking way is the current, make a newHTMLElement
for the text to be updated and set its styling but the ignored text remains the same. Thus the non-Arabic text is identical and only the Arabic text appears differently.Absolute worst case, we make a switch for both methods with users changing methods as they wish and we ship an optimal list of them. This means adding a new element to the database. But this would technically kind of fix #7 but not in the ideal way but would also significantly complicate the extension as users now have to understand how the extension works. Inconvenient, but again what's worse is that it's all not ideal, it's just a fix but not a solution.
While I hate having to accomodate for other site's weird behaviors, in this case I don't mind as much because I know the reason Google are doing this and I completely understand it and kind of support it if I am correct.
Extension is free but now our thousands of users have to see shitty ads on their Google search results (which Google themselves have no idea about) which we'll make (probably illegal and definitely unethical) money from. Imagine how far this could go, and all from a shitty extension that downloads videos or does YouTube analytics or whatever in which case...
Fuck you you filthy capitalist human garbage dirty cunt companies who make things worse for everyone for a quick (and small) buck.
Indeed, money is the root of all evil.
The text was updated successfully, but these errors were encountered: