Dynamic control bar width

[pixelipo]

Proposed solution for the issue found in #7478 by @MorrisJobke

[skjnldsv]

It's not going to float on top anymore on long scrolling lists though! :/

[pixelipo]

Yeah, I know :(

[MorrisJobke]

cc @nextcloud/designers

[jancborchardt]

:/ can we make both work? Cause we basically would trade "grid view switch not visible when there's a sidebar" with "neither breadcrumbs, upload, nor grid view visible when scrolled".

[MorrisJobke]

Sadly this is not supported in IE11 😢

https://caniuse.com/#feat=css-sticky

[pixelipo]

@MorrisJobke this will have really a minor effect for IE11 users (I think), no real degradation, so maybe it's still worth it? @jancborchardt ?

[MorrisJobke]

I need to test this.

[pixelipo]

Thanks @MorrisJobke - I would test it but I don't have a Windows computer available...

[MorrisJobke]

I'm fine with this for IE11. 👍

[pixelipo]

Turns out, we can, @jancborchardt ! I've made a commit here that fixes both problems :)

@skjnldsv@MorrisJobke please give feedback, but I suggest we merge this to the parent branch breadcrumbs-buttons-fixes-gallery and continue reviewing this over there.

[pixelipo]

One thing that might be worth noting:

On Windows 7, 8.1, and 10, only Internet Explorer 11 will receive security updates for the remainder of those Windows versions' support lifecycles.

Windows 7 is already in the "Extended support" (only security fixes).
Windows 8.1 will enter "Extended support" phase on January 10, 2018
Windows 10 uses Edge as a default browser.

I'm not sure if we are following OS support, but if so, IE11 should still be supported by us, but only on the "good enough" level.

This, of course, takes no account of Nextcloud's business, I'm obviously only speaking (daydreaming?) as a developer - if there are big organizations that rely on NC and use IE11, than non of that matters.

[MorrisJobke]

@skjnldsv Could we merge this? I added little fix (removed the z-index on the controls) to fix the behaviour in Safari and IE/Edge. (was working in Chrome)

[skjnldsv]

Damn, Just noticed we have a z-index issue: both at 50

[pixelipo]

@skjnldsv you can fix it over in #7478

[skjnldsv]

@pixelipo yup, done :)