I'm not really sure what to do about that, the change in this bug is a one-time thing, not something that is a "policy". Perhaps removing the policy would be an option, but that is error-prone and was attempted before.
Another solution might be to send a notification (something like "content-policy-override") that extensions can observe, making its' modifications as necessary. Would that be ok with everyone?
> > I can't seem to figure out how to detect an image rejection or success on the
> > image itself
>
> imageBlockingStatus?
(In reply to comment #59)
> See comment 46?
I'm not really sure what to do about that, the change in this bug is a one-time thing, not something that is a "policy". Perhaps removing the policy would be an option, but that is error-prone and was attempted before.
Another solution might be to send a notification (something like "content- policy- override" ) that extensions can observe, making its' modifications as necessary. Would that be ok with everyone?
> > I can't seem to figure out how to detect an image rejection or success on the atus?
> > image itself
>
> imageBlockingSt
Ok, I'll give that a shot. Thx.