markus-walther

**New test URL for reproduction:** https://patterns.axa.ch/?path=/story/examples-input-text-react--input-text-controlled-uncontrolled

Accepted, since I could reproduce it on MacOS Monterey 12.5.1 Safari Version 15.6.1 (17613.3.9.1.16).

@BeatHeierli I have taken the liberty to rewrite your title, preserving your intentions (I hope). Thanks for using our component and submitting your feature request! The Requirements section of the...

@BeatHeierli This is going to be reviewed by security people, the tightening to a few well-chosen MIME type was deliberate. I will update this ticket once a decision has been...

@MarekLacoAXA It seems **impossible** in general to omit a separator (of any kind, space being just one possible choice) between country-code part and local-phone-number part of a telephone-number _string_. This...

The original ticket description is ambiguous and imprecise. Here is a spec proposal: 1. Add new property **longestMatchParse** (default: false). 2. When longestMatchParse is truthy, augment the component's behaviour to...

@MarekLacoAXA Is the aforementioned spec good for you?

> > 1. Add new property **longestMatchParse** (default: false). > > I am not a fond of this. Would prefer to process numbers automatically instead. > APIs are a contract....

This is a consequence of violating https://github.com/axa-ch-webhub-cloud/pattern-library/tree/develop/src/components/20-molecules/input-phone#value requirements, i.e. no space between country code and local phone number. As such this is not a bug, since the behaviour is deliberate...

OK, I could reproduce it. Likely fix will be for the defaultValue case.