I have two questions about last updated. Now terrain and space travel fields for coordinates look to large. Hight is same, but length for those fields is increased, so they do look bit strange, at least to me. Was that by design, or simply came unintended with the rest?
Second question is about this:
"Tweaks: Prospecting action timer now shows up in members menu (Suggestion forum)"
It does not show up anywhere else except on its old place ( under Vehicle Controls > Cockpit ) for me. So, is it bug, or I've misunderstood something?
“Now terrain and space travel fields for coordinates look to large. Hight is same, but length for those fields is increased, so they do look bit strange, at least to me. Was that by design, or simply came unintended with the rest?”
Not sure what you mean. All the coordinate fields I've looked at seem fine? You'll need to provide a screenshot if you think there's an issue.
“It does not show up anywhere else except on its old place ( under Vehicle Controls > Cockpit ) for me”
It was accidentally added to a block of code that only appears on the dev server, so you'll need to wait for the next sync for it to actually appear over there.
Input boxes for numeric ranges were updated to be input type="number", rather than a selectbox, for various reasons from this bug: http://bugs.swcombine.com/view.php?id=4605 where a player using the old input boxes failed to trigger an important game warning.
If you click on the boxes now on mobile and other browsers it knows it will be numeric, so can give a customised input e.g. a keypad rather than a keyboard.
Man I haven't tried hyper yet since the sync but I just hope that was done for hyper travel as well, because those 1000-entry drop down boxes were hilariously dumb, and typing in them didn't actually work properly with the negatives.
I don't see any specific widths getting applied to it in the CSS, so chances are it's taking the browser's default width style instead of anything we've applied. I'm assuming that Chrome bases the width of a number input on the total number of values allowed in it (in our case, up to 2 characters), while FireFox/Edge/IE are forcing it to 100% the width of its container. This is different from selects in general because selects take the width of the longest content.
I'm guessing if we applied a width limit to the input boxes, it should get them all equal, but it's not really something that affects functionality.
Edited By: Ulrike Rayne Schultheiss on Year 19 Day 12 6:54 ____________