I can give more insight into this. The behavior people are complaining about appears to be a holdover from earlier windows builds designed to work with older single point/non multitouch displays
and is part of MS OS baked in gesture support. It affects both classic IE and MS Edge browsers where, only within the browser, any action perceived as a double tap/double click via the touch displayinitiates
a roughly 50% zoom over the current setting. A second double tap action restores the previous view. It is generally not a problem of touch
pads/other pointing devices, as these behaviors, if present and unwanted can typically be modified or disabled through the vendor supplied device driver UI available to the user. However, when
using a touch display, this particular gesture is handled by a MS bundled driver/gesture support engine and cannot be disabled.
In classic/desktop IE this behavior can be modified by using the custom style sheet: body { -ms-touch-action: manipulation; } which disables this touch display double tap input behavior while maintaining normal functionality with the vast majority of
websites (including google maps which I have noticed some style sheets that incorporate the -important command won't work properly).
However, the Edge browser does not support style sheets, and thus this behavior cannot be disabled via that method.
This behavior is set within all builds of windows that I can tell, both desktop and RT.
Many people using modern multi-touch displays do not appreciate the double tap to zoom behavior, myself included. On a larger multi-touch capable display, pinch zoom is the preferred method.
Now, I understand that MS would have concerns with older hardware (single point/non multipoint touch displays) where this behavior may be desirable. At some point the concept of streamlining across an infinite possibility of hardware configurations can
be taken a bit too far - the nature of the beast dictates, that unless MS exits the consumer/desktop OS market altogether, a fair amount of user configurability is and will always be necessary as the final user experience/appropriate behavior is effectively
not under MS control.