Bug 396416 - The mobile swipe item handles have issues with different sized entries
Summary: The mobile swipe item handles have issues with different sized entries
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: Master
Platform: Other Linux
: NOR normal
Target Milestone: Not decided
Assignee: Marco Martin
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-11 17:53 UTC by Emmanuel Lepage Vallée
Modified: 2018-11-12 16:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (9.95 KB, image/png)
2018-08-02 15:21 UTC, Marco Martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Emmanuel Lepage Vallée 2018-07-11 17:53:41 UTC
(disclaimer: This is a summary of a meeting discussion)

When using a list of swipe item with inconsistent height, the handles become all over the place instead of vertically aligned. This is because taller elements have a different kind of handle than the smaller one.

While equally sized elements are always preferred, it isn't always practical. For example, if a Ring-KDE account goes down, it need to be very explicit and an (/!\) emblem is added to the list and it increases the height a bit.

The point being it doesn't render correctly and it should. If I should find a better way to display the account list with consistent size is parallel to this bug.
Comment 1 Marco Martin 2018-08-02 15:21:14 UTC
Created attachment 114270 [details]
screenshot

this is how looks now with two items with different height, the handle seems to be fine?
Comment 2 Christoph Feck 2018-08-30 21:24:00 UTC
What is the status of this issue? If the presentation of the item handles is different from the screenshot in comment #1, please add your own screenshot, or clarify which issue you see there.
Comment 3 Christoph Feck 2018-09-13 16:02:44 UTC
If you can provide the information requested in comment #2, please add it.
Comment 4 Christoph Feck 2018-10-03 20:37:58 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 5 Andrew Crouthamel 2018-10-21 05:01:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2018-11-12 16:05:00 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!