Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thrusters module properties list has inconsistent capitalization #790

Open
QbranchFatherhood opened this issue Sep 28, 2024 · 4 comments
Open

Comments

@QbranchFatherhood
Copy link

The words "optimal" and "max" are lowercase in the list of Thruster module properties which is not consistent with the formatting of other info, nor with the properties of other core/optional/hardpoint modules which are consistently capitalized.

image

@alex-williams
Copy link
Collaborator

I cannot replicate this issue on a Windows PC using Chrome, Firefox, Opera or Edge browsers... please let me know the browser you're using to get this problem and I'll investigate further. If not, I'll close the issue.

@QbranchFatherhood
Copy link
Author

QbranchFatherhood commented Oct 22, 2024

The current version of Safari on iOS 18.

The discussion on the Discord revolved around this being a mobile-specific problem, and that the libraries for that are reportedly well out of date. So, testing on a PC likely wouldn't reveal anything.

@QbranchFatherhood
Copy link
Author

image

Max fuel for the FSD is "max Fuel".

@alex-williams
Copy link
Collaborator

The current version of Safari on iOS 18.

The discussion on the Discord revolved around this being a mobile-specific problem, and that the libraries for that are reportedly well out of date. So, testing on a PC likely wouldn't reveal anything.

Indeed, I've tested it on an Android device now too however and can't replicate the issue there in Chrome or Firefox either, so I'm leaning towards this being a Safari issue (It pops out most of the weird display bugs...) with the possibility that the React Libraries being out of date maybe being a contributing factor. Once I upgrade the libraries, I'll check back with you to see if it resolves the issue, but there isn't much else I can do if it's just a Safari bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants