B00ze64 opened issue desktopd/no-resource-uri-leak#17
Chrome In Content: Click-To-Play (pluginproblem)7 years ago
B00ze64 commented on issue desktopd/no-resource-uri-leak#11
DOM Inspector breaks when Chrome:// resources are blocked.They all do it differently. uBlock uses a browser tab for its preferences; the whitelist is a tab inside the browser tab with a HUGE textbox where you enter 1 domain per line. RAS has a small textblock and you have to enter all the sites in the JSON format which is a real pain. Cavas Blocker is the same as no-resource-uri-leak, there is a single-line-high textbox to enter websites separated with commas.
8 years ago
B00ze64 commented on issue desktopd/no-resource-uri-leak#11
DOM Inspector breaks when Chrome:// resources are blocked.Just noticed someone (7w2) posted a Stylish that applies the 3 CSS files for centering of images to well, images. I will thank him here; I don't like Discourse. I still think we should be able to expose specific resources, not just whole domains...
8 years ago
B00ze64 commented on issue desktopd/no-resource-uri-leak#11
DOM Inspector breaks when Chrome:// resources are blocked.Good day Neuemars,
8 years ago
B00ze64 opened issue desktopd/no-resource-uri-leak#11
DOM Inspector breaks when Chrome:// resources are blocked.8 years ago
B00ze64 commented on issue desktopd/no-resource-uri-leak#9
Flashblock breaks when Chrome:// resources are blocked.Can you help with some example? Because all I see is how to whitelist a DOMAIN so that presumably that domain has full access to all Chrome: and Resource: URIs. What we need is a way to make a specific Chrome: or Resource: available to all, instead of a way to make all available to a specific domain. Or am I understanding this all wrong?
8 years ago