Bugzilla

I suppose `-moz-windows-build` might actually be better yet. If implementing `-moz-windows-version`, would we be ultimately computing its value from the windows build number (e.g. I think win11 == 22000)? In OMC's message targeting we use the build number, and I noticed some test files on m-c using build number as a proxy for version number. If so, maybe using build number is simpler anyway?

I suppose `-moz-windows-build` might actually be better yet. If implementing `-moz-windows-version`, would we be ultimately computing its value from the windows build number (e.g. I think win11 == 22000)? In OMC's message targeting we use the build number, and I noticed [some](https://searchfox.org/mozilla-central/rev/0907529ff72c456ddb47839f5f7ba16291f28dce/widget/tests/browser/browser_test_scrollbar_colors.js#125) test [files](https://searchfox.org/mozilla-central/rev/0907529ff72c456ddb47839f5f7ba16291f28dce/browser/components/resistfingerprinting/test/browser/browser_navigator_iframes.js#89) on m-c using build number as a proxy for version number. If so, maybe using build number is simpler anyway?

I suppose `-moz-windows-build` might actually be better yet. If implementing `-moz-windows-version`, would we be ultimately computing its value from the windows build number (e.g. I think win11 == 22000)? If so, maybe using build number is simpler anyway? In OMC's message targeting we use the build number, and I noticed [some](https://searchfox.org/mozilla-central/rev/0907529ff72c456ddb47839f5f7ba16291f28dce/widget/tests/browser/browser_test_scrollbar_colors.js#125) test [files](https://searchfox.org/mozilla-central/rev/0907529ff72c456ddb47839f5f7ba16291f28dce/browser/components/resistfingerprinting/test/browser/browser_navigator_iframes.js#89) on m-c using build number as a proxy for version number. I can imagine some possible future use cases for selecting by build number, as we already target minor releases like 1903 or 1703 for message variants.