fix(css): fix misspelled properties

[oyo]

Description

Fixed properties written in kebap-case where camelCase is required

Why

In the browser dev tools we got an ugly warning message which is removed now.

Issue

n/a

Checklist

• I have followed the contributing guidelines
• I have performed a self-review of my own code
• I have successfully tested my changes locally

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[evegufy]

LGTM in general but even though this does seem like a small fix/change, IMO it's breaking, shouldn't the minor be raised? Be aware, we (portal app) aren't the only ones using this library.
And if we're already on spelling issues, could you maybe also search for "uploadProgess" and fix it? "Progress" is misspelled.

[oyo]

LGTM in general but even though this does seem like a small fix/change, IMO it's breaking, shouldn't the minor be raised? Be aware, we (portal app) aren't the only ones using this library. And if we're already on spelling issues, could you maybe also search for "uploadProgess" and fix it? "Progress" is misspelled.

@evegufy Increasing the minor version would be advised if any spelling in the interface to the library users has changed - but here I only fixed misspelled css attributes used within the components. So any code using the library is compiling as before, only the behavior of the component has slightly changed - not showing the warning in the dev console any more.

uploadProgess is such a case: changing this would require a minor version upgrade, another option would be to support both spellings - the incorrect and the correct one and set the incorrect to deprecated. That way existing code doesn't have to be changed immediately.

[evegufy]

@oyo thanks for the explanation!