Hm, I'm actually not sure what the best approach to take here is. I can't seem to find any examples of places where we disable single entries from content settings on pages. It seems like trying to do that may just incur all sorts of complexity we don't want. Any suggestions on how to approach this? Should we just ignore this and go along our merry way, since it's really up to the page to handle the API being unusable?

Drive by: Why not keep those settings in the bubble, but make them uneditable?

The reason I'm suggesting this is that we want to show the bubble for chrome-extension:// URLs ( bug 607261 ), and some settings such as images and JS aren't editable for extensions, so it would be nice to have some logic to do that.

Indeed, that seems like the best approach, although it also seems difficult, so I may not get around to this for a while. Thanks for the suggestion, meacer!

+1 we should do this. It shouldn't be too hard, it is just like things set by extensions, policy etc. that we handle already.

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!