Comment 4 for bug 1350817

The remark in the docs essentially just say that when antialiasing is used the color of the stroke's pixels is not necessarily the one you wanted. Which ... is kinda obvious. Most importantly, this is also a problem with SVG. And if you scale an image down.

In this case we're exporting an SVG image to XAML. It may have a specific size at which it is rendered or may be freely zoomable (the outer ViewBox element will scale anything inside anyway if it has to). But regardless, the stroke width constraints for the designer should be the same in SVG and XAML. If they want to ensure that strokes fit the pixel grid at a particular output size, then they should have done exactly that in SVG already (or use shape-rendering='crisp-edges' (which could very well be translated into SnapsToDevicePixels in XAML).

So I believe that the guideline in the documentation is more for designers to keep in mind that they don't do print. Also a stroke with thickness could appear in lots of places, be it a border around content, or part of a control template. I guess the SVG → XAML route only needs to concern itself with vector images and I'm not sure the suggestion in the docs holds much merit there.