Update to iD v2.9.0

[bhousel]

2.9.0

Jun 14, 2018

📣 Release Highlights

• 📷 We've added support for Bing Streetside! This new layer provides 360-degree panoramic imagery across large regions of the United States, United Kingdom, France, and Spain. Thank you, Microsoft!
  
  Activate the Bing Streetside layer by opening the Map Data pane (shortcut F)

🎉 New Features

• Add Bing Streetside data layer and service (#5050, thanks @jharpster, @shawnaparadee, @LorenMueller)
• Changed how icons and other graphics are bundled into iD (#3924)
  • Added support for more icon sets (such as FontAwesome) for presets or other iD icons (#3025)
  • Extracted many preset icons from the iD sprite into a separate project: bhousel/temaki
  • Many presets that previously did not have a suitable icon now have one.
  • ⚠️ All icons in iD now use prefixed names. (e.g. iD-, maki-, etc). See the preset README for more details.

✨ Usability

• When pasting a key=value string into tag editor, put key and value into correct fields (#5024, #5070, thanks @AndreasHae)
• Replace Mapillary street sign spritesheet .png with .svg (#4145)
  • Much sharper graphics
  • Adds support for many more street signs
  • Adds support for the Mapillary street sign layer in all browsers
• Render piers similar to other walkable features (sidewalks, rail platforms) (#5068, thanks @JamesKingdom)
• Support minValue/maxValue on numeric fields. Avoid negative values for many fields (#5043)

🐛 Bugfixes

• Fix bug causing icons not to update after a node drag (#5045)
• Fix tooltip location for data layers button (#5042, thanks @thomas-hervey)

🌏 Localization

• Add Australian address format (#5039)

🚀 Presets

• Add a window icon, use it for craft=glaziery and a few other presets (#5018)
• Allow power=pole preset for a standalone point (#5059, #5051)
• Add preset for shop=motorcycle_repair (#5054, thanks @demonshreder)
• Add preset for leisure=bleachers (#5031, thanks @rivermont)

[bhousel]

Heads up @tomhughes -
We discussed here a few weeks ago openstreetmap/iD#5040 (comment) - supporting Bing Streetside will require a new CSP rule.

The API endpoint we are hitting is here

I did try to get this working with XHR but it looks like the CORS headers aren't set up for this..

(Update: the existing virtualearth rule for Bing Metadata probably covers this)