You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The property Office.context.officeTheme is undefined when used in the Outlook application: Official documentation. In Word, Excel and PowerPoint, the property is defined and I can access its children properties (bodyBackgroundColor, controlForegroundColor, etc...). I tried with both latest (1.1.0.13) and previous (1.1.0.12) versions of Office.JS but it doesn't work.
Expected Behavior
The officeTheme property inside the context provides bodyBackgroundColor, controlForegroundColor, etc... in all applications
Current Behavior
The officeTheme property inside the context is undefined in Outlook
Steps to Reproduce, or Live Example
Office.initialize = function (reason) {
$(document).ready(function () {
// The "Office" object and its "context" property are valid but the "officeTheme" property is undefined.
// This works in Word, Excel and PowerPoint but not in Outlook.
if (!Office.context.officeTheme) {
console.log("Office theme not loaded");
}
});
}
Your Environment
PC desktop
Outlook 2016
Version 1711 Build. 8730.2127
The text was updated successfully, but these errors were encountered:
The property Office.context.officeTheme is undefined when used in the Outlook application: Official documentation. In Word, Excel and PowerPoint, the property is defined and I can access its children properties (bodyBackgroundColor, controlForegroundColor, etc...). I tried with both latest (1.1.0.13) and previous (1.1.0.12) versions of Office.JS but it doesn't work.
Expected Behavior
The officeTheme property inside the context provides bodyBackgroundColor, controlForegroundColor, etc... in all applications
Current Behavior
The officeTheme property inside the context is undefined in Outlook
Steps to Reproduce, or Live Example
Your Environment
PC desktop
Outlook 2016
Version 1711 Build. 8730.2127
The text was updated successfully, but these errors were encountered: