We run an internal web application that loads a lot of JS files including a file named heatmap.js. When the page loads, brave browser complains that Cross-Site tracker blocked and marks this file. Everything else loads fine.
We tried emptying out the file and loading the page - same issue - Brave complains again
We renamed the file to hm.js and left the original contents in there - No issue - Brave is fine
Is there a known issue about the filename heatmap.js?
Heatmap scripts are known as trackers, because of “heatmaps” are used by tracking mouse movements/actions on websites. Which are blocked by default, but renaming the filename to something different will get around the block.
But my friend heatmap is also used for a lot of other positive use cases. Reporting apps or other enterprise apps (like ours) might be showing genuine data to their users via heatmaps.
I think the correct way to block a tracker would be to first understand what the tracker does. And block that tracker if you see the symptoms instead of doing this based on filenames.
Do you have the logic of what constitutes tracking?
In that case, just disable site-trackers on the internal site, once we’ve fixed a bug with brave://adblock it should be easier to just whitelist the specific script