Yury Lebedev

`npm test` command exists in [package.json](https://github.com/Project-OSRM/osrm-frontend/blob/gh-pages/package.json#L7) so the project is almost ready for **Travis CI**. It's just necessary to upgrade [.eslintrc](https://github.com/Project-OSRM/osrm-frontend/blob/gh-pages/.eslintrc#L12) to replace obsolete `space-after-keywords` rule with something new: `keyword-spacing...

Actually there are no turn:lanes on the route except of [this part of Custer Road](https://www.openstreetmap.org/way/419510826#map=19/33.00706/-96.73380) (BTW with no lanes=4 tag) but U-turn maneuver here is on the next traffic lights...

I don't think this is really frontend issue - the 'Keep left' maneuver from backend is `slight left` but `turn:lanes` on [that link](https://www.openstreetmap.org/way/125885850#map=18/48.69009/6.11694) are `through|slight_right`. How frontend should suppose that...

Thanks @danpat for explanation but if I remove my hacks for opacity and maneuver icon, the `invalid` CSS does gray out lane icons:  `invalid` style fragment: ``` .invalid.lanes.leaflet-routing-icon...

Yes, we can :blush: 

@danpat, it seems `filter` doesn't work in IE11 :worried: Maybe we could use simple `opacity` instead?

I suppose the issue could be closed after merged #280

French is on place after implementing select-based language chooser (#228)

Looks good 👍

Actually yes, nobody usually asks for route for one language first and for another immediately after :wink: Then it just requires extending OSRM interface in another place - new optional...