Originally Posted by
LSG501
MS found that this div was interfering with edge and nothing more
"and nothing more" is the leap I have trouble making. MS isn't some all seeing deity, it is a bunch of people of varying skill levels and the usual mix of personality types and emotional baggage. They will indeed have tools to inspect code use, they must be whatever is built in to Edge else they can't see what is happening within Edge so you can play with those tools yourself. Personally I use the code inspection tools in Chrome and program in Linux, so I just wouldn't know if Edge is any good or not in that respect.
But we all know people who at the first hint of trouble throw their arms up and say "they did this to us on purpose, it isn't fair" and it just sounds to me like that is the most likely scenario here. It also sounds like they got an unfortunate person in the lucky dip of who they talked to in Google where let's face it they could have been a lot more useful. I would expect on a conversation like that to be given a Jira number of the raised bug report, not a brush off.
I see this as just people being people, not some corporate conspiracy. If you compare this to the Microsoft Halloween documents (yes that's a long time ago and I do believe Microsoft culture has improved a lot since then) that was a reaction to a definite and what at the time could be seen as an existential threat to Microsoft and so whilst I wasn't impressed with what they were doing I can understand how they got there. Compare that to what we are looking at here...
... what is Edge a threat to? Just how backed into a corner is Google?
If I was asked to list web browsers it would take me a while to even remember that Edge exists. I would probably list the likes of Netscape Navigator before I got to Edge. Google just don't have a fight here, at least not something worth any level of risk to their reputation from intentional dirty tricks.