Race condition for the navigator object about random-user-agent HOT 5 CLOSED

The problem appears on all sites where the user agent is evaluated during the page load. Due to the asynchronous nature of the callback passed to chrome.runtime.sendMessage the content script seems to run into a timing issue. Even though the script itself is executed before the page's Javascript, the callback function - which overwrites the user agent field - is called after the page's Javascript was executed and hence could potentially already fetch the untampered user agent.

This seems to be the case in both examples mentioned by @weranda, with internet.yandex.ru having additionally the issue listed at #24.

from random-user-agent.

#28 should fix this issue @weranda @tarampampam

There are still issues with embedded iframes though, which might not be fixable.

from random-user-agent.

There have been some issues with the fix (#28 (comment)) and the associated PR has been temporarily closed.

Any input on that issue would be appreciated (passing data in Chrome synchronously seems to be tricky)

from random-user-agent.

@neroux are you here, dude?

from random-user-agent.

@neroux 🔥 The fixed version (v3.2.0) has been released recently! Please check that everything is exactly as you wanted :)

from random-user-agent.