fix: justify-content property

[ahorek]

Description

fix a css property according to specs, no functional changes

Motivation and Context

• justify-content: none; is an invalid css, see https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content

How Has This Been Tested?

tested with and without servers (firefox and chrome)

Screenshots

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[glowcloud]

Thanks for the suggested changes!

Could I ask you to confirm if this issue still exists in the current versions of the browsers? I could not replicate the button moving to the left when loading a specification without schemes.

[ahorek]

@glowcloud thanks for looking into it.

I've double-checked and can't simulate the issue anymore, even with the old bundle. I'm on Firefox 122.0.1 now, so most likely they've fixed the issue on their side.

anyway, justify-content: none; should still be removed because it's invalid. Should I rebase the PR?

[glowcloud]

Thanks for the confirmation!
Please take a look at my comment.

[glowcloud]

Great, LGTM!