# [Bug] Missing Navigation and Non-Responsive Elements in “Volver al Catálogo de Aprendizaje” Section #1128
Assignees
spikerj (Joseph Spiker)
Clear assignees
spikerj (Joseph Spiker)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: spikerj/spikersoft-issues#1128
Reference in new issue
Block a user
Summary
The “Volver al Catálogo de Aprendizaje” button in the Patrones (Patterns) section does not have a dedicated navigation menu or functional link to access the catalog. Additionally, the listed elements within the section do not respond to user interaction.
Issue Description
In the Learn > Coding > Patterns module, the “Volver al Catálogo de Aprendizaje” button appears at the top of the lesson page but lacks a proper navigation route or menu integration. Clicking the button does not redirect to the catalog or trigger any visible action. Furthermore, the interactive elements within the catalog list (e.g., pattern items) fail to respond when clicked, suggesting broken or missing event handlers.
Environment
Preconditions
User must be logged in and have access to the Coding Patterns section.
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
High
Notes
The issue may be caused by missing route bindings or inactive click event listeners for the catalog navigation component. It is recommended to verify the routing configuration and ensure proper event handling for both the “Volver al Catálogo de Aprendizaje” button and catalog items.
Two claims here, and they came out differently — one is wrong, one is a good find.
The back link works.
"Volver al catálogo de aprendizaje"is arouterLinkto/classes, which is a real, unguarded route. Your own second screenshot is the proof: the address bar readsspikersoft.com/classesand the catalog is rendered behind it. So the click did navigate — I think the page simply looked unfamiliar, since the catalog is a plain list rather than the "menu" the ticket expected.A tip for next time: when a button seems to do nothing, check the URL bar in your after-screenshot. If it changed, navigation happened and the real question becomes "did the destination render what I expected" — a different bug with a different cause. You had already captured the evidence that answers it here.
The catalog items really are dead — confirmed. Across the whole 293-line catalog template:
And the stylesheet gives every row
cursor: pointeron hover, on top of the+icon. So the page actively signals "click me to expand" and then has nothing behind it. That is exactly what you hit, and it is worth fixing.There is a further wrinkle: the component already loads real course objects (with modules and lessons) into arrays that the template never uses, so the catalog is a mock-up sitting on top of real data.
What clicking should actually do — expand in place, or open a course page — is a product decision rather than something I should guess, so I have written it up with the options as spikerj/spikersoft-angular#914.
Leaving this open until the rows genuinely respond.
Status, 2026-09-13: part of this is now live on production. spikerj/spikersoft-angular#997 removed the hover pointer and the "+" affordance from the catalog rows, so the rows no longer look clickable when nothing happens on click.
The rows still don't do anything yet. Whether clicking should expand a course in place or open a course page is still a product decision, tracked in spikerj/spikersoft-angular#914. This ticket stays open until the rows actually respond. You don't need to re-report it in the meantime.
Tracker sweep 2026-09-27 — partially done.
Landed: The back link was never broken (the QA screenshot shows /classes). angular#997 (merged 2026-09-06) removed the
.b-course:hover { cursor: pointer }rules, and classes.component.css now has only the note 'no hover affordance'. But classes.component.html still renders<fa-icon [icon]="faSquarePlus">on all 33 rows (the 09-13 comment says '+' was removed; it wasn't), and no row has (click)/routerLink.Remaining: Catalog rows still don't respond. That depends on the A/B decision in angular#914. The square-plus icon still implies expandability.