The fixed 64px menu bar (--app-toolbar-height) requires each routed page to reserve its own top offset (pattern: padding-top: var(--app-toolbar-height, 64px), cf. platform-adoption/book-management). All five directly-routed Art Studio admin surfaces were built without it, so their page headers/content start underneath the menu:
Reported by Joey for art-presets/art-review/art-metrics; the other two share the identical structure. Not a #904 regression — the menu was fixed-position before the declutter; these pages simply never had the offset.
Complication: ArtMetricsDashboardComponent and ArtPipelineBuilderComponent are ALSO embedded as tabs inside ArtPipeShellComponent (tools outlet), so their :host offset must be reset by the shell to avoid double-padding there.
Fix: :host { display: block; padding-top: var(--app-toolbar-height, 64px); } on the five components + a padding-top: 0 reset on lib-art-metrics-dashboard / lib-art-pipeline-builder in art-pipe-shell styles.
The fixed 64px menu bar (`--app-toolbar-height`) requires each routed page to reserve its own top offset (pattern: `padding-top: var(--app-toolbar-height, 64px)`, cf. platform-adoption/book-management). All five directly-routed Art Studio admin surfaces were built without it, so their page headers/content start underneath the menu:
- /admin/art-review (ArtReviewQueueComponent)
- /admin/art-gallery-review (ArtGalleryModerationComponent)
- /admin/art-presets (ArtPresetManagerComponent)
- /admin/art-metrics (ArtMetricsDashboardComponent)
- /admin/art-builder (ArtPipelineBuilderComponent)
Reported by Joey for art-presets/art-review/art-metrics; the other two share the identical structure. Not a #904 regression — the menu was fixed-position before the declutter; these pages simply never had the offset.
Complication: `ArtMetricsDashboardComponent` and `ArtPipelineBuilderComponent` are ALSO embedded as tabs inside `ArtPipeShellComponent` (tools outlet), so their `:host` offset must be reset by the shell to avoid double-padding there.
Fix: `:host { display: block; padding-top: var(--app-toolbar-height, 64px); }` on the five components + a `padding-top: 0` reset on `lib-art-metrics-dashboard` / `lib-art-pipeline-builder` in art-pipe-shell styles.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The fixed 64px menu bar (
--app-toolbar-height) requires each routed page to reserve its own top offset (pattern:padding-top: var(--app-toolbar-height, 64px), cf. platform-adoption/book-management). All five directly-routed Art Studio admin surfaces were built without it, so their page headers/content start underneath the menu:Reported by Joey for art-presets/art-review/art-metrics; the other two share the identical structure. Not a #904 regression — the menu was fixed-position before the declutter; these pages simply never had the offset.
Complication:
ArtMetricsDashboardComponentandArtPipelineBuilderComponentare ALSO embedded as tabs insideArtPipeShellComponent(tools outlet), so their:hostoffset must be reset by the shell to avoid double-padding there.Fix:
:host { display: block; padding-top: var(--app-toolbar-height, 64px); }on the five components + apadding-top: 0reset onlib-art-metrics-dashboard/lib-art-pipeline-builderin art-pipe-shell styles.