Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Alter the layout of mobile view for end users #15017

Closed
designatedsuccessor opened this issue Jul 3, 2024 · 5 comments
Closed

Comments

@designatedsuccessor
Copy link

designatedsuccessor commented Jul 3, 2024

Is your feature request related to a problem? Please describe.

When an end user views their assigned assets on a phone, the layout changes from a table view to a list view. I understand the intent here, but I don't think the results are ideal for most users. The list is unnecessarily long because there is only one value per line. It's also a little difficult to immediately understand what you're looking at.

Describe the solution you'd like

I think most users would prefer an in-between where it may not be a full table like the desktop version, but it at least shows a column name and its corresponding value on the same row, as below:
image

Describe alternatives you've considered

No response

Additional context

No response

@MarcHagen

This comment has been minimized.

@snipe
Copy link
Owner

snipe commented Jan 13, 2025

@MarcHagen this is a pretty old (and unrelated) thread. If you're running latest on master, you should open a new issue.

@MarcHagen

This comment has been minimized.

@snipe
Copy link
Owner

snipe commented Jan 16, 2025

I've reacted on this issue as this is one a mobile improvement issue and second, not that old and still very relevant.

It's a completely different issue though, different screens and different reasons for the issue to have been created.

Opening a new issue will not help with the current 1.7K issue backlog. (not saying that that is bad or good!)

That's not necessarily true. Bugs take higher priority than feature requests, and things that can be done quickly will often get done sooner than larger things that take more time and planning (and vetting as a valid feature we want to do something with). Not to mention that we have different devs with different specializations. Assigning a smaller bug that's separate and isolated, versus "a change that would be nice to have" which requires a larger discussion on our end, is much more straightforward.

Please try to respect my requests as we try to help everyone as best as we can.

Please open a new issue and include the size and model of your phone so we can try to test and reproduce this. I cannot reproduce this on the iPhone 15 plus.

Image

@snipe
Copy link
Owner

snipe commented Jan 16, 2025

@designatedsuccessor - I hadn't noticed, but you're right - the way that library should be handling this is key/value on the same line. I'm not sure why our version of this isn't behaving this way, but we've opened an issue on our internal bug tracking system as well to see if we can get this fixed. (I don't think I quite understood the issue at first.)

This is the "normal" behavior: https://examples.bootstrap-table.com/#options/card-view.html
But ours isn't doing that - we're investigating why.

An extended Bootstrap table with radio, checkbox, sort, pagination, and other added features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants