Simon,

Its was not a bug. But we had missed out “markerBorderThickness” property in the example – default to zero if not set. Now I’ve updated the same. Please have a look.

Thanks for reporting.

—
Sunil Urs