(This is becuse they might have been deleted in a delete operation
and we are immediately redrawing the results of that operation before
reselecting something else)
(closes#2151), (see also d3/d3-zoom#60, d3/d3-brush#18)
Intercept `mousedown` and check if there is an orphaned zoom gesture.
This can happen if a previous `mousedown` occurred without a `mouseup`.
If we detect this, dispatch `mouseup` to complete the orphaned gesture,
so that d3-zoom won't stop propagation of new `mousedown` events.
Fixes an issue where a source might not compare strictly equal e.g.:
1. custom imagery gets blacklisted and replaced with a
`rendererBackgroundSource.None()`
2. which doesn't strictly === the `rendererBackgroundSource.None()` on the
background pane switcher
3. so the radio button would not appear checked
Previous code was problematic because we need the function to
to properly blacklist custom imagery passed in through the url hash,
before iD is completely initialized. Triggering GET causes tests to
break because osm service testing has side effects :-/
* Having separate presets for Surveillance and Surveillance Camera means
we can show the camera related fields only if `surveillance:type=camera`
* Generally use Upper Case for labels and keep it short
* if list of values is really fixed, use options strings to make them translateable
* if list of values is not fixed, avoid adding placeholder, iD will fetch from taginfo
* Seems like value "ALPR" is preferred over "alpr"
https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dsurveillancehttps://wiki.openstreetmap.org/wiki/Proposed_features/Extended_tags_for_Key:Surveillance
These are mandatory tags:
* `surveillance`
* `surveillance:type`
I do not feel that the following are important, they can be selected from
the drop down manually anyway:
* `operator`
* `name`
These tags are well established:
* `camera:type` has 15k users
* `camera:mount` has 13k users
* `surveillance:zone` has 17k users (mostly traffic is noted)
* `camera:direction` has 6k users
These tags are in the proposed status:
* `contact:webcam` usage is only starting
* `height`
People used various tags instead of `contact:webcam` in the past
because of it being a recent tag, and/or a lack of knowledge or being
mislead by the dropdown.
Thus it is difficult to quote an exact number, but by using complex
regexp queries, I could find thousands of usages for webcam links
when properly combining man_made/surveillance/camera and various
(sometimes invalid) keywords in the key or value part of a tag:
* `website`
* `image`
* `uri`, `url`, `link`, `http`, `contact`
* `stream`
* `webcam`