Using Edge and setting TrackingPrevention to False does nothing.
Developer log: Tracking Prevention blocked access to storage
1 Like
Can you please ellaborate?
You can consider this a false report. I believe it’s beyond the scope of the HTMExecutable setting and is quite possibly related to the way the Edge browser security operates. This behavior can be due to security policies, cached settings, or the nature of the resource being loaded, many variables. I found a way around the error using a different method… Sorry for the false alarm.
1 Like
You care to share with rest of us your solution? Be very helpfuf 
Yes, I just didn’t use it and did not have enough time to check whether it really is a bug or not, there’s so many variables as to why it might not work in all cases.
“I found a way around the error using a different method… Sorry for the false alarm.”
Okie Dokie. Not a clue what you are talking about, but I am old Just aksing what you used as your way around it. No big deal though.
1 Like