Improve mobile UI for files list

[AlexAndBear]

Description

This improvement solves the problem that files and folders with a longer name
than 10 chars will cut off to 7 chars by hiding non-essential meta data.
This is unwieldy to navigate through files and folders.
As well the uploading indicator text on a folders table row will now be
displayed at the beginning to avoid UI glitches.

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Screenshots (if appropriate):

Before

After

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[AlexAndBear]

@pmaier1 cool with it?

[ChrisEdS]

Technically approved.

[phil-davis]

Thinking out loud - I wonder what we should do about testing that the webUI "behaves nicely" when being displayed on a smaller device/window? It would be possible to run some CI with a smaller-sized browser window, but we can also just leave it to manual smoke-test to be done during release QA.

[AlexAndBear]

@phil-davis Do we have similar tests already, how much effort do you think is required for a full coverage?

[phil-davis]

@phil-davis Do we have similar tests already, how much effort do you think is required for a full coverage?

In web we set an env var, for example, "SCREEN_RESOLUTION": "375x812" to test with a mobile-phone-sized screen.

Here in the "traditional" oC10 UI we can do similar. Code like this resizes the window:
$this->getSession()->resizeWindow(375, 812, 'current');

We can add some code to do that if SCREEN_RESOLUTION is set. And then run whatever subset of test scenarios we like in CI with whatever SCREEN_RESOLUTION settings.

The "problem" is that we keep adding more CI pipelines! So maybe we just do it for a set of "smokeTest" scenarios.

I raised issue #38759 for that. Does not need to happen for this PR!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
No Duplication information

[AlexAndBear]

@pmaier1 waiting for your go 👍

[pmaier1]

@pmaier1 waiting for your go

Fine for me 👍