KvadrantMetrics
Page and control measurements, in dp at the canonical 0.75 of Metro's pixels.
Only what is used so far. A token added before something reads it is a number nobody has checked.
focusRingThickness is the one exception to the first sentence and says so in its own doc: it comes from the Windows 8 lineage rather than the phone's, where a pixel is a different length, so it is converted by a different factor. Everything else here is a Metro phone pixel × 0.75.
Constructors
Properties
PhoneBorderThickness 3 px — a Metro button's border, and it is thick on purpose.
PhoneButtonBase's Padding="10,3,10,5" — the button's content inset, asymmetric top to bottom.
The dotted keyboard-focus ring's stroke, and the one number here that is not a phone pixel.
PivotHeaderItem padding 21,0,1,0 — the 21 px is the gap between headers.
PivotItemMargin 12,28,12,0.
The progress bar's one dimension: a dot is Width="4" Height="4" and both rectangles of the determinate track are Height="4", so it is a single number in three places.
Height="12" on the slider's track and fill — not the progress bar's 4.
How far a pressed surface sinks — MaxDepression = 25 Metro pixels.
Extended to the modern minimum, always — visual stays canonical. See D7.
PhoneTouchTargetOverhang 12 px: the invisible padding around a small target.
The canonical touch target. Authentic; touchTargetMin is what is actually enforced.