Commit c45c6c55 authored by Nate Graham's avatar Nate Graham 🔩
Browse files

Comment out Page toolbar style in preparation for the bug being fixed

We don't want these views to suddenly have an auto-generated header in
addition to the custom one; we will need to do some porting work first
to get everything wired up correctly before we can display the
auto-generated header and delete the custom one.
parent d56076e3
Pipeline #52294 passed with stage
in 9 minutes and 47 seconds
......@@ -49,6 +49,8 @@ Kirigami.Page {
// FIXME: Apparently the page needs to have a row or a stack to show the
// header toolbar automatically, so we have to make our own See
// https://bugs.kde.org/show_bug.cgi?id=432541
// globalToolBarStyle: Kirigami.ApplicationHeaderStyle.ToolBar
header: ToolBar {
Layout.fillWidth: true
......
......@@ -49,7 +49,6 @@ Kirigami.Page {
title: i18nc("@info Title of the view of the playlist; keep this string as short as possible because horizontal space is quite scarce", "Playlist")
globalToolBarStyle: Kirigami.ApplicationHeaderStyle.ToolBar
padding: 0
// Use view colors so the background is white
......@@ -104,6 +103,8 @@ Kirigami.Page {
// FIXME: Apparently the page needs to have a row or a stack to show the
// header toolbar automatically, so we have to make our own See
// https://bugs.kde.org/show_bug.cgi?id=432541
// globalToolBarStyle: Kirigami.ApplicationHeaderStyle.ToolBar
header: ToolBar {
// Override color to use standard window colors, not header colors
// TODO: remove this if the HeaderBar component is ever removed or moved
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment