[fields] Fix field editing after closing the picker

[LukasTy]

Fixes #12652.

Clicking the open button causes the following event to be triggered and if default is not prevented, it executes the input DOM selection logic.

mui-x/packages/x-date-pickers/src/internals/hooks/useField/useFieldV6TextField.ts

Lines 248 to 257 in f617d70

	const handleInputClick = useEventCallback((event: React.MouseEvent, ...args) => {
	// The click event on the clear button would propagate to the input, trigger this handler and result in a wrong section selection.
	// We avoid this by checking if the call of `handleInputClick` is actually intended, or a side effect.
	if (event.isDefaultPrevented()) {
	return;
	}
	onClick?.(event, ...(args as []));
	syncSelectionFromDOM();
	});

Changed the onOpen and onClose actions to call event.preventDefault() to avoid such problems.

[mui-bot]

Deploy preview: https://deploy-preview-12675--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against bf0d93d

[flaviendelangle]

@LukasTy the e2e tests are broken 👍

[LukasTy]

the e2e tests are broken 👍

@flaviendelangle This is a totally random problem that made no sense to me... 🙈 🤷
Simply renaming the test file helped to avoid this problem... 😆
This just makes my argument for going with the native playwright test writing style stronger. 👍

[flaviendelangle]

Simply renaming the test file helped to avoid this problem... 😆

😭

[flaviendelangle]

Do we have places where we pass the event to onClose?
This PR only passes them to onOpen

[LukasTy]

Explicitly nope, but implicitly it is called by clicking on the open picker button and this is basically the reason why our selection indexes get screwed up... 🙈
Without this, the fix doesn't work as the input selection logic gets called.

[flaviendelangle]

OK make sense 👍