MokoConsulting/MokoCassiopeia
1
1
Fork 0
Code Issues 4 Pull Requests Actions Packages Releases 1 Activity

QA: Verify sticky header fix on staging #116

New Issue
Closed
opened 2026-04-03 06:16:50 +00:00 by jmiller-moko · 3 comments
jmiller-moko commented 2026-04-03 06:16:50 +00:00 (Migrated from github.com)
Copy Link

Weekend QA Checklist

The sticky header was fixed in commit 628a99c (CSS specificity issue). Needs manual verification on staging/production.

Test Steps

  • Enable sticky header: System > Site Templates > MokoCassiopeia > Theme > Sticky Header > Yes
  • Scroll down on desktop — header should stick to top of viewport
  • Check z-index: header should stay above dropdowns, modals, and offcanvas drawers
  • Check mobile (< 992px) — header should not be sticky (reverts to static)
  • Check that non-sticky mode still works: set to No, header should scroll away normally
  • Check dropdown menus still open correctly when header is sticky
  • Check that the header background image/shadow still renders correctly

What Was Changed

  • Removed position: relative from .container-header in template.css (was overriding .sticky-top)
  • Added .container-header.sticky-top rule with z-index: 1020
  • Mobile media query now only disables sticky when .sticky-top class is present

Related

## Weekend QA Checklist The sticky header was fixed in commit 628a99c (CSS specificity issue). Needs manual verification on staging/production. ### Test Steps - [ ] Enable sticky header: **System > Site Templates > MokoCassiopeia > Theme > Sticky Header > Yes** - [ ] Scroll down on desktop — header should stick to top of viewport - [ ] Check z-index: header should stay above dropdowns, modals, and offcanvas drawers - [ ] Check mobile (< 992px) — header should **not** be sticky (reverts to static) - [ ] Check that non-sticky mode still works: set to **No**, header should scroll away normally - [ ] Check dropdown menus still open correctly when header is sticky - [ ] Check that the header background image/shadow still renders correctly ### What Was Changed - Removed position: relative from .container-header in template.css (was overriding .sticky-top) - Added .container-header.sticky-top rule with z-index: 1020 - Mobile media query now only disables sticky when .sticky-top class is present ### Related - Fix commit: 628a99c - Original issue: #115
jmiller-moko commented 2026-04-04 20:04:37 +00:00 (Migrated from github.com)
Copy Link

Update: Additional fixes deployed to dev/03.09.01

The sticky header fix from 628a99c is deployed. Additionally, the following related changes have been made in this development cycle:

Main menu link color fix

  • Header nav links were showing body link color instead of --mainmenu-nav-link-color
  • Added explicit .container-header .nav-link CSS rule (commit 4801571)

Back-to-top link

  • Icon changed from IcoMoon icon-arrow-up to FA fa-solid fa-arrow-up
  • Added id="top" anchor to header for no-JS fallback

QA still needed

All original test steps remain valid. The sticky header, menu colors, and back-to-top should all be verified on the dev server.

## Update: Additional fixes deployed to dev/03.09.01 The sticky header fix from 628a99c is deployed. Additionally, the following related changes have been made in this development cycle: ### Main menu link color fix - Header nav links were showing body link color instead of `--mainmenu-nav-link-color` - Added explicit `.container-header .nav-link` CSS rule (commit 4801571) ### Back-to-top link - Icon changed from IcoMoon `icon-arrow-up` to FA `fa-solid fa-arrow-up` - Added `id="top"` anchor to header for no-JS fallback ### QA still needed All original test steps remain valid. The sticky header, menu colors, and back-to-top should all be verified on the dev server.
jmiller-moko commented 2026-04-04 21:42:25 +00:00 (Migrated from github.com)
Copy Link

Update: 2026-04-04 (Session 2)

Additional header/nav changes deployed that affect QA:

  • Bootstrap collapse loaded — hamburger menu now functional on mobile (was broken due to missing HTMLHelper::_('bootstrap.collapse'))
  • Hamburger icon — now uses Font Awesome fa-bars instead of Bootstrap SVG
  • Sticky header — confirmed disabled on mobile (position: relative at < 992px), sticky on desktop only
  • Nav link colors — .container-header .nav-link and .container-nav a now explicitly use --mainmenu-nav-link-color
  • Search module — full width in header search position at all breakpoints

Updated QA Checklist

  • Sticky header works on desktop, scrolls away on mobile
  • Hamburger menu opens/closes on mobile (tap the FA bars icon)
  • Menu links are white (or nav color) in header, not body link color
  • Search bar stretches full width in the nav area
  • Back-to-top button scrolls to top (FA arrow-up icon visible)
  • Sidebar modules show as accordions (open on desktop, collapsed on mobile)
## Update: 2026-04-04 (Session 2) Additional header/nav changes deployed that affect QA: - **Bootstrap collapse loaded** — hamburger menu now functional on mobile (was broken due to missing `HTMLHelper::_('bootstrap.collapse')`) - **Hamburger icon** — now uses Font Awesome `fa-bars` instead of Bootstrap SVG - **Sticky header** — confirmed disabled on mobile (`position: relative` at < 992px), sticky on desktop only - **Nav link colors** — `.container-header .nav-link` and `.container-nav a` now explicitly use `--mainmenu-nav-link-color` - **Search module** — full width in header search position at all breakpoints ### Updated QA Checklist - [ ] Sticky header works on desktop, scrolls away on mobile - [ ] Hamburger menu opens/closes on mobile (tap the FA bars icon) - [ ] Menu links are white (or nav color) in header, not body link color - [ ] Search bar stretches full width in the nav area - [ ] Back-to-top button scrolls to top (FA arrow-up icon visible) - [ ] Sidebar modules show as accordions (open on desktop, collapsed on mobile)
jmiller-moko commented 2026-04-07 22:42:23 +00:00 (Migrated from github.com)
Copy Link

Closed — sticky header verified working on desktop, disabled on mobile as intended. All QA items addressed in v03.09.01 release.

Closed — sticky header verified working on desktop, disabled on mobile as intended. All QA items addressed in v03.09.01 release.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 bug
Something isn't working
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention is needed
 html
HTML template changes
 invalid
This doesn't seem right
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 major-release
Major version release (breaking changes)
 minor-release
Minor version release (XX.YY.00)
 mokostandards
MokoStandards compliance
 needs-changelog
needs-review
Awaiting code review
 needs-testing
Requires manual or automated testing
 patch-release
Patch version release (XX.YY.ZZ)
 php
PHP code changes
 priority: critical
Critical priority, must be addressed immediately
 priority: high
High priority
 priority: low
Low priority
 priority: medium
Medium priority
 push-failure
File push failure requiring attention
 python
Python code changes
 question
Further information is requested
 regression
Regression from a previous working state
 release
Release related PR
 release-candidate
Release candidate build
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 standards-violation
Standards compliance failure
 status: blocked
Blocked by another issue or dependency
 status: in-progress
Currently being worked on
 status: on-hold
Temporarily on hold
 status: pending
Pending action or decision
 status: wontfix
This will not be worked on
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 test-failure
Automated test failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: release
Release preparation or tracking
 type: test
Test suite additions or changes
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-branch
Version branch related
 version-drift
Version mismatch detected
 version-update
Version bump and release PR
 wontfix
This will not be worked on
 work-in-progress
Work in progress, not ready for merge
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No Label ci-cd html joomla priority: critical type: bug type: test
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoCassiopeia#116
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?