Shelf's tags don't follow the hierarchy ... #5569

New Issue

OVERLORD · 2026-02-05T10:10:38+03:00

OVERLORD commented

2026-02-05 10:10:38 +03:00

Originally created by @DoctorRetromaker on GitHub (Jan 15, 2026).

Describe the Bug

Shelf's tags don't follow the hierarchy schema, just dead at shelf level .... is this a bug or a intentional feature?

Steps to Reproduce

Set any tag at shelf level
open a book inside the shelf
check with any developer tool the book body element; there isn't any shelf-tag-name- class ....

Expected Behaviour

Since the shelves are a part of the hierarchy established by Bookstack, it would be desirable to have a behavior of the tags similar to that observed in the other elements.

And, how about to add «application level» tags?

Screenshots or Additional Context

No response

Browser Details

Brave 1.85.120 (Chromium 143.0)

Exact BookStack Version

25.12..1

Originally created by @DoctorRetromaker on GitHub (Jan 15, 2026). ### Describe the Bug Shelf's tags don't follow the hierarchy schema, just dead at shelf level .... is this a bug or a intentional feature? ### Steps to Reproduce 1. Set any tag at shelf level 2. open a book inside the shelf 3. check with any developer tool the book `body` element; there isn't any `shelf-tag-name-` class .... ### Expected Behaviour Since the shelves are a part of the hierarchy established by Bookstack, it would be desirable to have a behavior of the tags similar to that observed in the other elements. And, how about to add «application level» tags? ### Screenshots or Additional Context _No response_ ### Browser Details Brave 1.85.120 (Chromium 143.0) ### Exact BookStack Version 25.12..1

OVERLORD added the 🔨 Feature Request label 2026-02-05 10:10:38 +03:00

OVERLORD commented

2026-02-05 10:10:39 +03:00

@ssddanbrown commented on GitHub (Jan 22, 2026):

Hi @DoctorRetromaker,

This is intentional, since content within shelves isn't currently considered to belong to a specific shelf (a looser relationship).

I've therefore recategorised this to a feature request, since this isn't a break in existing functionality.

And, how about to add «application level» tags?

Without knowing the purpose, That would seem a little redundant to me, since you could just write customisations which apply globally anyway, that's the default really.

@ssddanbrown commented on GitHub (Jan 22, 2026): Hi @DoctorRetromaker, This is intentional, since content within shelves isn't currently considered to belong to a specific shelf (a looser relationship). I've therefore recategorised this to a feature request, since this isn't a break in existing functionality. > And, how about to add «application level» tags? Without knowing the purpose, That would seem a little redundant to me, since you could just write customisations which apply globally anyway, that's the default really.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#5569