[openstreetmap/openstreetmap-website] Directions geocoding doesn't take current location into account (#2327)

[mtmail]

**Issue**

While the search endpoint (`GeocoderController`) sends the current map bounding box to the geocoder (Nominatim), the geocoding AJAX request in `directions.js` doesn't.

**To reproduce**

Normal search
1. Search for Manchester https://www.openstreetmap.org/search?query=manchester
2. Search for King Street https://www.openstreetmap.org/search?query=king+street
3. a King Street in Manchester is found (https://www.openstreetmap.org/way/4961636)

vs

Directions search
1. Search for Manchester https://www.openstreetmap.org/search?query=manchester
2. Open directions dialog, it shows start and destination fields. Start is now prefilled with `Manchester, Greater Manchester, North West England, England, United Kingdom`
3. In the destination field type in "King Street" and press `[TAB]` or unfocus the input field
4. a King Street in Derby is found, far away

**Expected behavior**

King Street near Manchester should be set as destination. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2327
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190724/f45b9fec/attachment.html>