Our last meeting was very short because we had no new issues to triage. Today's meeting isn't terribly long but we had a bunch of issues to triage, though only a few we could take action on.
util:InternetShortcut IconFile attribute not modularized and formatted when in merge module, from @chrpai, requests support for
InternetShortcuts in merge modules. We took the issue into WIX v4.
Burn implementation hangs on pipe.Write(), from @skylarnam, with a follow-up post on the wix-devs mailing list, suggests an issue when using Burn's named-pipe communication support. There isn't a clearly-identified bug yet, so we're keeping this issue open until we know more.
Logging password variables using WiX managed bootstrapper, from @jenniferrs, turns out not to be a bug because Burn variables are case-sensitive.
Make Feature/@Absent and Feature/@AllowAdvertise consistent, from @robmen, wants to turn the
Absentattribute into a plain boolean (
no) rather than its current custom boolean (
disallow). That will go into WiX v4.0.
Accessibility - Pop up window has same text, from @jithinjosepkl, suggests that a cancellation confirmation window should have a different title. We agreed and took the issue in WiX v4. Anyone can make that change in their own loc strings too.
Accessibility: Narrator reads decorative image as text, Accessibility: Narrator does not read contents in confirmation window, Accessibility: Tooltip does not appear on keyboard focus, Accessibility: ScreenReader does not convey information about the required fields, Accessibility: Narrator does not read checkbox, Accessibility: Name property of EndUser agreement is missing, Accessibility: Zoom in does not work, Accessibility: Narrator does not read button text, Accessibility: Narrator does not read license , and Accessibility: progress bar elements are incorrect all report various accessibility issues with an MSI's internal UI. Unfortunately, internal MSI UI is controlled at runtime by Windows Installer and it's limited in its accessibility support. WiX, being a humble build tool, can't change the behavior of MSI internal UI as it has no extensibility model. Of course, a bootstrapper application for a Burn bundle can do whatever it wants to do for accessibility.
As Rob predicted last week, there was no progress on Votive for Visual Studio 2019. However, the Build conference is over and Rob has time with Microsoft experts on Visual Studio extensibility on Friday. With a little luck, he'll get the help necessary to make the Votive templates look better and he can wrap up Votive for Visual Studio 2019.