Extend rule syntax

[0xBRM]

... to include 'fonts', 'websockets', 'pings', and so on, so forth -- e.g. * * websocket block

I understand the popup UI is not wide enough to accomodate so many object types, which are in turn classed as 'other', but as it stands, extending the rule syntax would better make use of the request listener (since they're already intercepted anyway) by increasing the granularity, and no one would be forced to block a varied number of objects, just to block websockets (whilst allowing pings, for instance).

I don't have any ideas for the logger, perhaps a second logger-only matrix? An expandable 'other' column that allows you to select a more specific class of objects?

[stryx]

I'm using uMatrix with quite restrictive default settings (essentially only 1st-party html, css+fonts and images are allowed) and manual exceptions, along with uBlock origin for static filter lists (and in particular strict blocking). I had been wondering for quite a while why uMatrix lumps together CSS and fonts. CSS is often necessary to view a page, whereas fonts usually are as dispensable. Therefore, a few days ago I changed the settings of uBlock origin to block all fonts by default (no-remote-fonts: * true). As a result, I have to keep track of manual exceptions on a per domain basis in both uBlock origin and uMatrix. To me it would make more sense to use uBlock origin for static filter lists only (plus maybe a few very elementary manual mechanisms for people who don't want to install uMatrix) and leave all the more fine-grained manual control to uMatrix.

[0xBRM]

@stryx I think css and fonts are lumped together due to space restrictions, hence this request. It would also justify the existence of the my rules pane, as it would actually extend the functionality of the matrix.

[slycelote]

Looks like HTML5 video is included into "others" too. Doesn't make sense IMHO, it's logically the same as images.