Description of the bug
When creating a User compare context (to compare my user account to the user account for the profile page I am viewing, for example) I noticed that even though contexts were marked as required, the visibility condition is still visible in the drop-down menu.
This new visibility condition has two required user contexts, so should not be available on any path without a user context (the second user context is global $user and is always available). Yet it appears in the select list for the home page layout.

Steps To Reproduce
To reproduce the behavior: 1. Apply the patch from https://github.com/backdrop/backdrop-issues/issues/4029 2. Manage blocks on the home page layout 3. Attempt to add a visibility condition
Actual behavior
- Confirm that
User: compareappears in the list
Expected behavior
Since User: compare appears in the list has required contexts that are not present, User: compare should NOT appear in the list of available visibility conditions
Recent comments
I am considering migrating my drupal 7 website to backdrop. Hi @seamus, I would like to offer my professional services for migration to BackdropCMS. Please connect If...
drupal 7 to backdrop migration
Restore Newsletter Subscriptions from a Database Backup One of my websites was affected by the Simplenews issue, and there were many incorrectly disabled newsletter subscriptions of '...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
This is the report about the recently discovered bug: https://github.com/backdrop-contrib/simplenews/issues/83. First, how do you know if your site is affected? In other words: Are there...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled