Describe the bug
The algorithm behind the discoverRootDomain functionality checks if the domain is valid to set a cookie at the highest level domain. This algorithm currently starts from a eTLD which will not be valid in any case, e.g. .com, .io etc.
This behaviour will create a console warning every time in some browsers e.g. Firefox
The fix would just be to start trying from the TLD and not the eTLD.
Note
Even with the fix, if we have an eTLD with more than one part e.g. co.uk, then the warning will still be there. This happens with other trackers as well e.g. analytics.js
Describe the bug
The algorithm behind the
discoverRootDomainfunctionality checks if the domain is valid to set a cookie at the highest level domain. This algorithm currently starts from a eTLD which will not be valid in any case, e.g..com,.ioetc.This behaviour will create a console warning every time in some browsers e.g. Firefox
The fix would just be to start trying from the TLD and not the eTLD.
Note
Even with the fix, if we have an eTLD with more than one part e.g. co.uk, then the warning will still be there. This happens with other trackers as well e.g. analytics.js