Something is very weird about window displays in general. Take the list of wi-fi networks; sometimes the entire thing will just stop appearing, doing nothing when you click the icon! I eventually figured out that if I use Windows Search to pull up the WiFi Settings panel, and manually click the list of networks there, then the list is fixed (it does not appear in the Settings window though; it just pops up where it was supposed to be, near the taskbar icon).
I just don’t understand; I cannot fathom what implementation could be so complex that they can’t achieve full test coverage on something like whether or not a damned window appears when required.
> I cannot fathom what implementation could be so complex that they can’t achieve full test coverage on something like whether or not a damned window appears when required.
It does seem that complicated from my observations. Notice that it's not a regular window, but part of the overriding/overlayed renderer (DWM? something else?) that draws stuff on top with grayscale smoothing (Direct2D? DirectWrite? something else?)... which probably involves lots of communication between several processes. It feels like an incredibly heavyweight UI component, just judging from the lag between when the icon is clicked and when the list of networks pops up.
The QA team got folded into the main org a while ago. I'd be surprised if the person today in charge of the full test coverage has anywhere near the resources or weight to make an impact.
I just don’t understand; I cannot fathom what implementation could be so complex that they can’t achieve full test coverage on something like whether or not a damned window appears when required.