fix(css): correct boundaries of breaking points

[susnux]

• Resolves: [Bug]: File names are covered by side bar if browser window is 1024 pixels wide #56861

Summary

We mixed the logic of breaking points (when to break), this makes it consistent:
Mobile breaking point is 1024px, so it is applied to width < 1024 and starting with 1024 its "normal".

So we consistently have:
width < 512px: small mobile
512 <= width < 1024px: mobile
width >= 1024px: normal

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

[susnux]

/backport to stable32

[susnux]

/backport to stable31

[solracsf]

/backport a95d781 to stable32

[susnux]

/backport a95d781 to stable32

[susnux]

/backport a95d781 to stable31

[mijutu]

Is this fix supposed to work now? I just upgraded to 33.0.3 and I'm still having side bar over file names.

The screenshot is from a new profile in Firefox that was just created and was never used with any other nextcloud version.

I didn't try with a new nextcloud instance.

[susnux]

Is this fix supposed to work now? I just upgraded to 33.0.3 and I'm still having side bar over file names.

Yes it is fixed. The sidebar by design overflows the content if the screen width is < 1024px

[mijutu]

But I'm not seeing any difference to the situation before the fix.
If browser window is narrow, then file names are visible, like before.
If browser window is wide, then file names are visible, like before.
If browser windows is 1024 pixels wide, then file names are covered by the side bar, like before.

Compare my first screenshot with these two:

[susnux]

But I'm not seeing any difference to the situation before the fix.

Its only about the exact size of 1024px, there the behavior was wrong.