fixes a bug where in case multiple items with the same `value` are present in the combobox' dropdown, always the first one is returned in the `accept` event
fixes#12060
This bug can occur occasionally under the following circumstances:
* map feature 1 is selected
* the cursor is in an address (sub) field
* map feature 2 gets selected directly
* now, in some cases, the contents of the address fields of feature 2 are written into feature 1's tags
* Field: fix wikiURL by URL encoding it - and slight refactors
* Field: fix wikiURL only encodeURIComponent instead of redundant full URL
* Field: refactors function to generate wikiURL, ensures anchor part is also URI encoded, ensures the anchor ref is not encoded, adds unit tests
* Field: refactors wikipedia URI encoding of the anchor logic, removes legacy anchorencode effort via try-catch that replaced percentage character with dots, adds unit further tests, reduces exessive inlining
* Fields: Break long lines in combo dropdown instead of ellipsis
Longer translations keys are not readable with ellipsis and the tooltip only shows the description (or fallback), not the title.
This change makes long use line breaks with small line height to make the whole text visible.
* Fields: Use table styles for rows to maximize available space
The flex box solution gave a lot of space to the label. This solution minimizes that space to give more space to the values dropdown.
Most DMS format parsed by @mapbox/sexagesimal,
add a expandable matcher and two new formats for coordinates in DMS format in search bar
example: `35 11 10.1 , 136 49 53.8` (D M SS format), or `35 11.168 , 136 49.896` (D MM format)
The common use case is for the `sources` key, often you have multiple URLs separated with semicolon.
This allow to navigate to URL and check them more easily instead of
doing manual work to select the URL copy and paste.
Created with the help of Martin Raifer at the sotmeu2023!
fixes#9898
Fixes a problem that occurs because the order of the field `options`
can be in general different from the order returned by taginfo
(taginfo sorts by usage, while presets typically are sorted alphabetically),
causing different values to be potentially selected for autocomplete values.
As the taginfo results typically come in a few moments delayed, this can
lead to confusing behaviour.
This solves it by just not reattempting an autocomplete using the taginfo
results, if a field has static options available.
