when user logs out of osm.org via the logout button: the popup continues to the login screen, which if completed now logs the user back into iD with the new credentials
closes#10634
This happens for example when the tooltip are rendered for the map controlls (right or left edge of the screen depending on user locale): If the anchor is close to the bottom of the screen, the tooltip would be placed not ideally in the corner and hard to read. It is solved by falling back to left/right tooltips with a potentially offset arrow in these cases
closes#10624
The misalignment happens because the origin offset is not properly accounted for boxes around map coordinates, when the map surface is itself offset from the top-left corner of the map. This can happen with customized installations of iD, e.g. the version built into the HOT tasking manager.
fixes bug: if there were extra rendering surfaces loaded, e.g. the one of the turn restriction editor, the walkthrough tooltips and the curresponding masks were inadvertently rendered to that secondary surface, which can be even offscreen
* Pass the reference explicitly to the function to ensure the correct context is available.
* refactor: handle blur() in a closure to separate UI logic from addMembership
* spacing
* Fixed typo
---------
Co-authored-by: Deeptanshu Sankhwar <deeptanshu@walletsocket.com>
Co-authored-by: Minh Nguyễn <mxn@1ec5.org>
* iD#8707 Show ref in the name of route relations
* Avoid combining PTv2-formatted name with ref
* Pair name with other tags when labeling routes
---------
Co-authored-by: Kyle Hensel <k.y.l.e@outlook.co.nz>
and use fully quoted strings for cases which have characters that need to be encoded
old: tag=foo\"bar\" -> new: tag=foo"bar" or tag="foo\"bar\""
old: tag=foo\nbar -> new: tag="foo\nbar"
falls back to raw tag values if a quoted string cannot be parsed
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
