we proudly established a permissions system that obeys the abstraction pattern
access > permissions > roles > users

the "block visibility by role" feature circumvents this abstraction, by doing
access > roles > users

what looks easier in the first place and a victory of pragmatism over complex academic principles,
becomes a major PITA in practice:

know what happens if a sitebuilder adds a role, sets all permissions and... there's hidden permission stuff with blocks?

ever had to tell your child (or customer) why that role that has all permissions does not see block X?

we really do not want to start building hidden permision systems.

or the other way round:
"access by permission not roles"
like
"program against interfaces not classes"

Comments

marcingy’s picture

Category: bug » task

Moving to task this makes sense but nothing is actually broken at the moment.

geek-merlin’s picture

Category: task » bug

forgot to add a constructive proposal:
implement one view permission per block

geek-merlin’s picture

Category: bug » task

ups, postings crossing.

geek-merlin’s picture

Issue summary: View changes

added programatic eclipse

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

tim.plunkett’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

This has been in block.module as long as I have been using Drupal. I'm going to call this a lost cause.
Please reopen if you feel strongly about it though!