In KDE, I was able to add graphic elements (monitoring memory, hardisk, etc) and while I was adding elements to panel, the width of each one was automatically widened or narrowed in order to see completely of all them. That's not working in Plasma 5. Graphic elements are cropped or even out of sight and morevover they are hidding the "Panel configuration" button cause they are over it. Reproducible: Always Steps to Reproduce: 1.Add monitoring graphic elements to horizontal panel till you begin to lose they of your sight. Actual Results: Graphic elements are lose of sight. Expected Results: To widen or to narrow automatically each graphic element to get them fit on panel width.
Created attachment 93608 [details] Plasma 5.3.2 - Graphic elements in panel are not narrowed to fit panel width
Created attachment 93609 [details] KDE 4 - Panel with a lot of graphics elements correctly auto adjusted
Each applet specifies it's own size, if other applets do things wrong they need separate bug reports please.
KDE Frameworks 5.24.0 and this bug still not resolved. Is not a specific applet bug, but a general System Applet's mistake. As you can see in previously attached images, KDE 4 did not oversize applets width, like Plasma DOES. User CAN'T CONTROL those applets width, but KDE4 did a excellent on this and all applets fitted perfectly in my 1024 width screen. Now, is impossible. There is no possibility for the user to change width or to avoid show the applet tag. Please, fix this bug.
(In reply to David Edmundson from comment #3) > Each applet specifies it's own size, if other applets do things wrong they > need separate bug reports please. The applets that do this bad work come with Plasma. How to contact with their developers? I can't find something like "applet" in bug reports.
This possibly could be a Panel bug - for allowing widgets to go beyond panel width
Sadly, this bug (being and applet's bug or plasma bug) is still not fixed. Like the panel between two monitors. Plasma is pretty is pretty than KDE, but work worse for sure. It's a pity.
Seems to be fixed now.
Thank you, I am afraid I must wait for next OpenSUSE stable version to see that issue is solved.