How to permanently allow blocked objects?
How to permanently allow blocked objects?
For an already whitelisted site? Big PITA to have to go through this each time I open a particular site.
And is there a way to permanently allow only a single blocked object, or a selection of blocked objects (but not all) for an already whitelisted site?
Why is the only option to temporarily allow a blocked object? Why isn't there an option to permanently allow?
And is there a way to permanently allow only a single blocked object, or a selection of blocked objects (but not all) for an already whitelisted site?
Why is the only option to temporarily allow a blocked object? Why isn't there an option to permanently allow?
Last edited by kukla on Thu Jun 09, 2016 2:43 pm, edited 1 time in total.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
about:config > noscript.allowedMimeRegExp
If you want to allow only specific objects from those sites, or allow the objects on a per-site basis, you'd have to combine that with ABE rules.
If you want to allow only specific objects from those sites, or allow the objects on a per-site basis, you'd have to combine that with ABE rules.
*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
Thanks. First, have zero ability with reg ex, so that one is out. Second, I would need some help to do this in ABE. In order to learn how to do this, can you tell me what I would enter there with these two selected (arrows) blocked objects, and what I would enter in ABE in order to allow all.barbaz wrote:about:config > noscript.allowedMimeRegExp
If you want to allow only specific objects from those sites, or allow the objects on a per-site basis, you'd have to combine that with ABE rules.
Also, perhaps for Giorgio, can we have an option to permanently allow, not just temporarily allow a blocked object? Why do all of these have to be temporarily allow? We have permanently allow for a script.

Last edited by kukla on Thu Jun 09, 2016 2:57 pm, edited 1 time in total.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
For the first arrow, you'd type that as-is replacing the '.' with '\.'
The second arrow I don't know to enter it into allowedMimeRegExp. You might try this:
or this
re: ABE rule, that would only be useful for if you want to block these objects on other than the specific site you want them Allowed. Can't help you there without more specifics as to what site you're looking at and what other sites you'd want the objects Allowed on, sorry.
Code: Select all
FONT@https://discussions\.apple\.comCode: Select all
.*@https://www\.apple\.comCode: Select all
*@https://www\.apple\.com*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
If you mean in the NS menu, viewtopic.php?f=10&t=20514kukla wrote:Also, perhaps for Giorgio, can we have an option to permanently allow, not just temporarily allow a blocked object? Why do all of these have to be temporarily allow? We have permanently allow for a script.
*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
Think that's what I was asking for, but looks like it never got done, or even got any real attention. Just don't understand why the only option for allowing a blocked object (with "Apply these restrictions to whitelisted....") is Temporarily allow.barbaz wrote:If you mean in the NS menu, viewtopic.php?f=10&t=20514kukla wrote:Also, perhaps for Giorgio, can we have an option to permanently allow, not just temporarily allow a blocked object? Why do all of these have to be temporarily allow? We have permanently allow for a script.
And thanks for the reg ex. I entered both of those comma separated and it looks like at least one of those did the job.
.*@https://www\.apple\.com, *@https://www\.apple\.com
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
You're welcome. 
(allowedMimeRegExp entries should be space-separated not comma-separated)
(allowedMimeRegExp entries should be space-separated not comma-separated)
*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
Changed to space separated, but seems it worked either way. Maybe it just ignored the second one after the comma, which wasn't needed anyway, and just used the first. But even if I knew reg ex, this is definitely a big PITA to have to do this for regularly visited whitelisted sites. I have to have "Apply these restrictions...." checked in order to have a placeholder show for all Flash content.barbaz wrote:You're welcome.
(allowedMimeRegExp entries should be space-separated not comma-separated)
Giorgio, how about doing something about this?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
I think it would have discarded the one with the comma because that matches literally the site "https://www.apple.com,", which doesn't exist. So the second entry is the correct one.kukla wrote:Changed to space separated, but seems it worked either way. Maybe it just ignored the second one after the comma, which wasn't needed anyway, and just used the first.
(atm he's pretty busy designing WebExtensions API... anyway, you might have better luck getting his attention by bumping the other thread. idk.)kukla wrote:Giorgio, how about doing something about this?
*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
OK, will bump that thread and hope for the best. I understand how that new Web Extensions API will be keeping him busy. Shame how it's going to destroy many addons.
And yes, seeing how it would take that string literally as the URL with the comma included.
But now something quite strange, as a possible side effect of entering that, or anything, in noscript.allowedMimeRegExp.
With that entered (.*@https://www\.apple\.com *@https://www\.apple\.com), not getting any placeholders for Flash content. Removed and tested and the placeholders were back.
Why would that be happening? And not only that, but not entirely sure of this, since I didn't look everywhere, was no longer getting any blocked objects for any sites I visited after entering that string.
And yes, seeing how it would take that string literally as the URL with the comma included.
But now something quite strange, as a possible side effect of entering that, or anything, in noscript.allowedMimeRegExp.
With that entered (.*@https://www\.apple\.com *@https://www\.apple\.com), not getting any placeholders for Flash content. Removed and tested and the placeholders were back.
Why would that be happening? And not only that, but not entirely sure of this, since I didn't look everywhere, was no longer getting any blocked objects for any sites I visited after entering that string.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
Just tested on speedtest.net. Double, triple checked. Adding that entry to noscript.allowedMimeRegExp definitely removes the Flash Player placeholder where it normally would appear, as well as removing any Blocked Objects, not just for the Apple site, but as far as I can tell, any site. Very weird.
Will have to live with temporarily allowing those Blocked Objects at Apple, since having a placeholder for possibly dangerous Flash Player content is much more important.
Will have to live with temporarily allowing those Blocked Objects at Apple, since having a placeholder for possibly dangerous Flash Player content is much more important.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
Yeah that is odd, maybe allowedMimeRegExp doesn't support wildcard MIME type? Probably another bug...
The specific *@https://www.apple.com in your screenshot only looks to apply to a FONT object, so you could try adding this instead of all the other suggested entries?
The specific *@https://www.apple.com in your screenshot only looks to apply to a FONT object, so you could try adding this instead of all the other suggested entries?
Code: Select all
FONT@https://(?:discussions|www)\.apple\.com*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
Yeah, that seems to have done the job. Getting placeholder for Flash and Blocked Objects menu now for other sites. Many thanks for the help.
Also added to that feature request thread
viewtopic.php?f=10&t=20514&p=83232#p83232
Also added to that feature request thread
viewtopic.php?f=10&t=20514&p=83232#p83232
Last edited by kukla on Thu Jun 09, 2016 6:19 pm, edited 1 time in total.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0
Re: How to permanently allow blocked objects?
You're welcome!
*Always* check the changelogs BEFORE updating that important software!
-
Re: How to permanently allow blocked objects?
And a little late, but one more thing: I have never really understood what "objects" are. I know the Blocked Objects sub-menu wasn't there years ago, when I first started using NS. Perhaps you can direct me to something to read about this (not finding anything), or offer a quick explanation. In addition, referring to my screenshot, above, can you explain why there are so many different versions of what appear to be the same FONT object.
And sometimes, even if I allow a particular object, when the page reloads the exact same one will reappear, as if it had never been allowed.
And sometimes, even if I allow a particular object, when the page reloads the exact same one will reappear, as if it had never been allowed.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Firefox/45.0