Fixes Issue 35286 Firefox inconsistent scrolling

[sorbaugh]

• Resolves: [Bug]: Firefox inconsistent scrolling #35286

Summary

URL: #35286

Adding overflow-anchor: none to #app-content element within files.scss and re-minified files.css and merged.css.

Tested on Firefox 111.0 (64-Bit)

TODO

• ...

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)

[artonge]

Can you also run npm ci and npm run build, and also amend your commit with a sign-off? Otherwise, CI will not pass.
https://github.com/nextcloud/server/pull/37297/checks?check_run_id=12112120394

[sorbaugh]

Hello! I ran npm run build as requested, which altered 98 files in the /dist directory of my fork. The purpose of these changes seem to be mainly for cache-busting / adding a new version number to the source-mapping url.

Since I'm new to contributing in nextcloud and the main change is so small, it feels kind of overkill to commit this many files. So before I commit I wanted to ask if this is ok?

Best regards

[artonge]

Since I'm new to contributing in nextcloud and the main change is so small, it feels kind of overkill to commit this many files. So before I commit I wanted to ask if this is ok?

Indeed, not the best, but this is how we currently do things :) So you can commit and push those files.

[sorbaugh]

Ok I assume the conflicts with the /dist directory were to be expected if npm run build is run frequently :)

If everything else is alright and ready for merge, I can do a rebase.

[artonge]

If everything else is alright and ready for merge, I can do a rebase.

Yes, please rebase, compile, commit and push again :)