Allow this behavior to be optional by route

Created on 6 June 2023, over 1 year ago

Problem/Motivation

We have some sites that make use of the contextual tabs block for end-user functionality on some areas of the site. This is particularly common with the User page and User editing tabs, and with the Login/registration forms. Pushing these elements into the "tidy" sidebar is confusing to the non-administrative users of the site.

Steps to reproduce

Enable the module on a site, log in as a site user or go to the user login screen and look for the "reset password" or "register" tabs. They are hiding!

Proposed resolution

Provide the same contextual filtering behavior that you get on the block edit screen somehow. Maybe this could be by adding a block that includes the JS and CSS rather than adding it universally, and leveraging the existing block context configuration options.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States gcb

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @gcb
  • πŸ‡ΊπŸ‡ΈUnited States gcb
  • πŸ‡ΊπŸ‡ΈUnited States bdimaggio Boston, MA

    I like this! Would be nice too if there were a default configuration included that, on installation via a post-update hook,
    1. placed the block in the installing site's user-facing theme automatically (in say the first available region--doesn't matter because the CSS takes care of presentation)
    2. set block visibility so that by default, this only showed up on node view pages. Could restrict by page and choose node/* or, if that's too broad, restrict by content type and auto-choose all available content types.

Production build 0.71.5 2024