Skip to content

Conversation

@tsukuha
Copy link

@tsukuha tsukuha commented Dec 17, 2025

close: #14032

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Documentation
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

QInput clearable func is changed its default null to empty string when input type is 'text', 'search', 'url', 'tel', 'password', or textarea.

The PR fulfills these requirements:

  • It's submitted to the dev branch (or v[X] branch)
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on a Cordova (iOS, Android) app
  • It's been tested on an Electron app
  • Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

@tsukuha tsukuha changed the title fix(QInput): #14032 change q-input about type text clearValue() default null to empty string fix(QInput): change q-input about type text clearValue() default null to empty string(#14032) Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using clearable in masked input set model to empty string instead of null

1 participant