Bug 462301 - ActionToolBar has no reasonable default size
Summary: ActionToolBar has no reasonable default size
Status: CONFIRMED
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: Master
Platform: Other Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-27 09:09 UTC by Kai Uwe Broulik
Modified: 2022-11-30 20:55 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Screenshot of ActionToolbar in KCM (30.67 KB, image/png)
2022-11-27 09:09 UTC, Kai Uwe Broulik 		Details
qml for testing (462 bytes, text/x-qml)
2022-11-27 09:26 UTC, Matej Starc 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2022-11-27 09:09:27 UTC 
Created attachment 154075 [details]
Screenshot of ActionToolbar in KCM

SUMMARY
Trying to use a Kirigami.ActionToolBar in a KCM header/footer results in it being squished to nothingness

STEPS TO REPRODUCE
KCM.SimpleKCM {
    footer: Kirigami.ActionToolBar {
                flat: false
                alignment: Qt.AlignRight
                actions: [ ... ]
    }
}

OBSERVED RESULT
Control is squished and unusable

EXPECTED RESULT
Control has a reasonable default size

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: git master as of 2022-11-21

ADDITIONAL INFORMATION
Comment 1 Matej Starc 2022-11-27 09:26:59 UTC 
Created attachment 154076 [details]
qml for testing

we use this file for testing this.
Comment 2 Matej Starc 2022-11-27 09:41:01 UTC 
For some reason, it works in my case. 

Operating System: Arch Linux
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.9-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz
Memory: 15,5 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics
Comment 3 Nate Graham 2022-11-30 20:55:36 UTC 
Yeah you need to use layout properties (which we do in the KCMs that have it already implemented), but I agree it should have a sensible implicit size