Document / Disable the ability to select viewing node entities.

@Grevil: Shouldn't remove access content permission work?

I'd expect that the status is then NEUTRAL and can be set by our module. Or does that legacy code return DENIED explicitly?

But yes, correct, I ran into this issue some weeks ago, if ACCESS permission is given anywhere, there's no way to revoke it anymore. So definitely access content must be false for tests.
On top Node uses Grants etc. so it's absolutely possible we can't fix it here and should postpone this issue, but please try without the "access content" permission first (if you didn't already).

@Anybody view node should not be selectable, that's all. So no need to postpone this issue.

You can test it yourself:

user permissions ['access content', 'edit article'] => /node/1/edit => access allowed

user permissions ['edit article'] => /node/1/edit => access denied

WITHOUT any modules activated outside the core modules.

user permissions ['access content', 'edit article'] => /node/1/edit => access allowed

user permissions ['edit article'] => /node/1/edit => access denied

in the 2nd one you allowed "edit" using our field then?

Confirmed. So this extra case *might* be excluded by a special condition and documented, but for now I think we should postpone this, at least technically.

If someone runs into this confusion, he can write a fix for this to be reviewed.

@Anybody, no simply using the "edit article" permission provided by core.

Basically, we can not access any content without "access content". Another example: We have an authenticated user, without the "access content" permission, who IS allowed to view a node (through our field), since he does NOT have the "access content" permission, permission is denied.

But thinking this through, it might make more sense to just display a warning, that this special case exists for nodes?