PATCH CORE: customfields - leave never-set numeric fields unset, only clear reused widgets

et2_customfields_list.set_value() coerces missing (and falsy) stored values
to null before pushing them into the per-field child widgets. For float/int
custom fields the child is an et2-number, whose value setter runs the value
through parseFloat: parseFloat(null) parses the string "null" and yields
NaN, so the input displays the literal text "NaN" and the subsequent save
fails the pattern validation.

Per review on upstream PR EGroupware#269: don't turn "not yet set" into "set as
empty" - a pristine widget is left completely untouched on null. A plain
skip is not enough though: preview / CRM-style views reuse one widget
instance across records via set_value(), and skipping there would leave the
previous record's number displayed on a record where the field is unset.
So null is skipped only while the widget shows nothing, and clears it
otherwise.

The switch matches "number" as well, because _setup_float/_setup_int
rewrite field.type on the shared field object during row creation.

Upstream PR EGroupware#269, replacing the Et2Number-side approach of PR EGroupware#268.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
(cherry picked from commit 581153c)

Author: asig2016

api/js/etemplate/et2_extension_customfields.ts

@@ -637,6 +637,24 @@ export class et2_customfields_list extends et2_valueWidget implements et2_IDetac
 
 			switch(this.options.customfields[field_name].type)
 			{
+				case 'float':
+				case 'int':
+				case 'number':	// _setup_float / _setup_int rewrite field.type to "number" on row creation
+					// et2-number renders null via parseFloat as the literal "NaN".  Leave a
+					// never-set field alone instead of turning "not yet set" into "set as
+					// empty", but a reused widget still showing the previous entry's number
+					// (preview / CRM-view row clicks) must be cleared
+					if(value === null)
+					{
+						const widget : any = this.widgets[field_name];
+						const current = typeof widget.getValue === "function" ? widget.getValue() : widget.value;
+						if(current === "" || current === null || typeof current === "undefined")
+						{
+							continue;
+						}
+						value = "";
+					}
+					break;
 				case 'date':
 					// Date custom fields are always in Y-m-d, which seldom matches user's preference
 					// which fails when sent to date widget.  This is only used for nm rows, when possible