fix(pat-select2): Show predefined value for single-select widgets.

[thet]

Single-select widgets did not show their predefined value. This is now fixed.

fixed:

not fixed:

• I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
• I verified there aren't any other open pull requests for the same change.
• I followed the guidelines in Contributing to Plone.
• I successfully ran code quality checks on my changes locally.
• I successfully ran tests on my changes locally.
• If needed, I added new tests for my changes.
• If needed, I added documentation for my changes.
• I included a change log entry in my commits.

---

If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.

Closes #

[petschki]

Shouldn't that be a <select> if its not multiple values ?

I wonder why this is needed, because the language field actually works with predefined values: https://github.com/plone/plone.app.dexterity/blob/master/src/plone/app/dexterity/behaviors/metadata.py#L110

[thet]

A‌ <select> field cannot use AJAX‌ remote data.

And for the timezone selection fields I do not want to use pre-populated list of options - because it can be huge - but a text field where you can enter manually (if JS is off) or search/select via AJAX.

[petschki]

that makes totally sense

[petschki]

/run-coredev-robottests

[thet]

/run-coredev-robottests

[thet]

@petschki

Btw. I have added a test showing that the <select> field isn't broken with this PR.
But thanks for the fixes in the querystringwidget!

[petschki]

LGTM