Office does a lot of things their own way and without a lot of the cross-compatibility that's a feature of most Microsoft products.
That's why you'll find you'll be able to do something in Office, but other Microsoft programs won't. Or vice versa.
Like Notepad and Internet Explorer are pretty much just containers for certain Windows controls. Controls Office don't use. They roll their own. Or at least, used to. Wouldn't surprise me to find out that Office had their own browser rendering engine that didn't rely on anything in IE.
> Wouldn't surprise me to find out that Office had their own browser rendering engine that didn't rely on anything in IE.
I'm not sure what the situation is now, but for a long time Outlook used MS Word, not MSIE, to render HTML email messages. Word is a terrible web browser, so that made it next to impossible to design templates for things like email newsletters that would look & behave sensibly in Outlook.
Outlook 2003 switched to the IE renderer, then for what I consider to be terrible reasons they switched back to MSO in 2007, and still use it in Outlook and even Windows Mail now. (The reasons I recall were bugs in the editor and security—.)
For people that aren’t in the know: the MSO engine is basically a very incomplete and quite buggy implementation of the HTML 3.2 specification. From where I stand, it looks like the entire thing is a binary blob that essentially hasn’t been touched at all for over twenty years. Literally.
Microsoft switching back to MSO breathed new life into an entire industry of people with esoteric, hard-won knowledge about the eldritch affairs of HTML for email. Without it, HTML for email would not be such a disaster. (Sure, there are other awful email clients, but Outlook is by far the most terrible that is used much these days. If it had tightened its game, other bad clients would have been much more like to fix theirs too.)
> Office does a lot of things their own way and without a lot of the cross-compatibility that's a feature of most Microsoft products.
That's probably because unlike most Microsoft products, Office is cross-platform and has to support multiple operating systems, including MacOS, iOS, and Android.
Isn't Office for Mac a completely diverged fork from an old Windows version of Office? I remember some blog posts from the understaffed Mac Office team stating that much several years ago. I don't know if they rebased it in the meantime. The posts read as if the big Office team was focused entirely on Windows and everything else was done by understaffed teams struggling to keep up.
Not anymore. From what I’ve been told from an insider, the latest versions are derived from a common code base now, with platform specific bits separate for each platform.
The latest office for Mac looks quite a bit like the windows version now (for once) so it’s not too surprising.
Office does a lot of things their own way and without a lot of the cross-compatibility that's a feature of most Microsoft products.
That's why you'll find you'll be able to do something in Office, but other Microsoft programs won't. Or vice versa.
Like Notepad and Internet Explorer are pretty much just containers for certain Windows controls. Controls Office don't use. They roll their own. Or at least, used to. Wouldn't surprise me to find out that Office had their own browser rendering engine that didn't rely on anything in IE.