John Firebaugh

I just discovered that my issues seem to be entirely due to llvm.org taking extremely long to connect (30+ seconds), such that `apt-get update` just skips the sources: ``` W:...

llvm.org is down again today, breaking builds. Still looking for a solution here if anyone has one.

@dirk -- APT caching "is available only for private repositories."

Someone deleted the entire http://llvm.org/apt/ subdirectory today, again breaking all Travis builds that use the whitelisted packages.

It looks like llvm.org is no longer going to host packages: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html

Upstream PR which this depends on: https://github.com/mapbox/geojson-vt/pull/60.

Based on https://github.com/MicrosoftEdge/Status/issues/336#issue-128272670, the sentence "Support is currently limited to only devices with a touchscreen (can be overridden in about:flags)." is also incorrect or at least misleading.

I've seen something very similar in iD and have a hunch that there was a recalculate style-related performance regression somewhere in the last several Chrome versions. Worth checking Chrome Canary.

No, couldn't really say. Do you know a good way of testing old Chrome versions? I wanted to do that but they seemed very difficult to obtain.

`.leaflet-dragging` is also sometimes used in app CSS to implement effects like "hovering" a marker during drags.