The content scripts on IE can access any window variables from the webpage it runs, meaning I can read the page's jQuery or any other window variables they might have. This causes conflict issues where the libraries hosted on the webpage may conflict with the libraries used in the content scripts.
I reckon this is why jQuery needs to be declared using noConflict on content scripts as well, on IE.
The content scripts on IE can access any window variables from the webpage it runs, meaning I can read the page's jQuery or any other window variables they might have. This causes conflict issues where the libraries hosted on the webpage may conflict with the libraries used in the content scripts. I reckon this is why jQuery needs to be declared using noConflict on content scripts as well, on IE.