Support

I cannot reproduce your issue. Custom values are saved just fine.

I would normally be asking you if any other settings are saved, but you have said yourself that other predefined values are saved.

Here's why your ticket makes no sense to me. What is actually saved is the number, regardless of whether it's chosen from a drop-down or entered directly in the interface.

The interface is rendered with JavaScript. The code there is really simple. It creates a drop-down with the different predetermined values, and an input box which holds the actual value. When the interface is created it checks the value against the predefined ones. If that's the case, it marks the corresponding drop-down value as selected. Then that happens, the custom value checkbox is hidden.

When you select a predefined value, the JavaScript code updates the value in the custom value box (which is hidden). That is the value which will be saved to the database; the drop-down does not participate, it's just an interface element.

When you select the Custom option in the drop-down, all the JavaScript code does is unhide the input box which holds the value and revert said value to what was selected when you first loaded the page.

This code has been there since December 2009. It's been used on millions of sites over the last 14 years.

If no value, predefined or custom, was saved I could understand the problem: it would be a matter of saving the settings which we can troubleshoot. But a problem where predefined values work and custom values don't does not make sense. It would mean a bug in the JavaScript code which has not changed in years, nobody else has reported, and I cannot reproduce. Therefore, that's an impossibility. I could also suspect a weird network caching issue which would cause the submitted form to always send the same old data, but then you wouldn't be able to save any of the predefined values either. Therefore, that's an impossibility as well.

Are you ABSOLUTELY SURE (please test again, carefully) that you can save predefined values? If you tell me that this definitely happens I cannot really explain what is going on, because we have run out of logical explanations as to what is going on, and right into the territory of someone having tampered with the JavaScript code we use.

Okay, that makes far more sense. The edit box (and the value spinner, what you call arrows) are rendered and handled completely by the browser. It is an input box of the type number. The fact that changing the input box' value with the spinner does not update its value, or at least does not trigger the onchange event, is a browser issue we cannot do about.

All we can tell you to do it not use the spinner buttons on Firefox on Windows 10.

Changing our software for a browser and OS combination that's about 0.5% market share, and especially because said browser has a bug? That's not going to happen. It makes no sense removing client-side validation for such a fringe issue that's not even remotely related to anything we do.