The table in the what's new page is to tight on small screens

[anthonydillon]

Describe the bug

The key information on the what's new page is not accessible on small screens.

To Reproduce

Steps to reproduce the behavior:

1. Go to https://vanillaframework.io/docs/whats-new on a phone
2. See the version and other important information is truncated

Expected behavior
I should be able to see the all the information as it's key content.

Screenshots

Additional context

The status key below is easy to read and looks nice (if that helps at all)

[elioqoshi]

@lyubomir-popov @bartaz quick draft. Would it be structurally okay / possible to merge the status and version values as part of the component? They feel more like labels than needing their own column:

Alternatively we could include them in the table from the start in this manner?

Anyhow, quick two options with 1 having the description underneath (not sure if this is possible as part of a table component or whether that's the right approach though).

2 merges status and version into the component field which I think could work out better.

[lyubomir-popov]

What's the point of the version column? We have one table per release, so you can remove the version column altogether.

[elioqoshi]

Good point. Not sure how it ended up there or whether it was automatical. Thought there might be some sub-version releases which might be relevant?

Regardless, even if that's removed there is still space lacking

[cristinadresch]

@bartaz any thoughts?

[bartaz]

@elioqoshi

Overall I think version column is valuable, while we keep separate table for latest release, we do merge all previous releases into one long table, like here with 2.0:

It is valuable to have this version information. While not ideal, we probably can hide version on small screens (because it's definitely supplementary information).

Visually I like your proposal of having notes below rest of the data, but I don't think it would be easily achievable with HTML table now.

Second option to merge status label and version into one cell seems interesting compromise.

The issue is from implementation point of view we don't have much flexibility to change table layout on different screen sizes, so we would need to explore that.

[bartaz]

Triage: Low effort, low impact: As a quick fix we could apply the horizontal scroll as in other places in the docs.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/WD-15186.

This message was autogenerated