pepso
commented
4 months ago Hi @exextoc,
I understand the underlying JS engine the Classic Outlook launch events uses is based on V8, and by default the i18 / Intl support should be enabled during the compilation time. Does the ICU 75 update from April explain the dropped support?
Do we expect the support for Intl in Classic Outlook to be back in the upcoming Outlook releases?
We resorted to implement our Add-in without Intl package dependency for non-marketplace clients. We'd love to know this before we update the marketplace manifest version listing.
I noticed the current channel release notes were talking about character issues and decided to update the Outlook to the latest version and can confirm our add-in is still executed in an environment without Intl package:
Following code in action function:
console.log("Testing Intl Support...");
console.log("Intl typeof?", typeof Intl);
console.log("Intl available?", Intl ? true : false);Results to following OfficeAddins.log.txt entries:
12/07/2024 11:36:51 Verbose Runtime [Console] [Log] Testing Intl Support...
12/07/2024 11:36:51 Verbose Runtime [Console] [Log] 'Intl typeof?', 'undefined'
12/07/2024 11:36:51 Verbose Runtime [Console] [Log] ReferenceError: Intl is not defined
12/07/2024 11:36:51 Unexpected Runtime [Error] [Log] ReferenceError: Intl is not defined
Object.h [as error]
foundation.win32.bundle:57:1965
Object.error
C:\FOLDER\bundle.js:53:24
Object.error
C:\FOLDER\bundle.js:66:22
_callee$
C:\FOLDER\bundle.js:7640:12
tryCatch
C:\FOLDER\bundle.js:7581:1061
Generator.<anonymous>
C:\FOLDER\bundle.js:7581:3007
Generator.next
C:\FOLDER\bundle.js:7581:1698
asyncGeneratorStep
C:\FOLDER\bundle.js:7582:69
_next
C:\FOLDER\bundle.js:7583:162
u
foundation.win32.bundle:70:156
ztcdsb
Provide required information needed to triage your issue
Your Environment
Expected behavior
Using Intl package (and its DateTimeFormat, NumberFormat, ListFormat) works as before.
Current behavior
Before updating the outlook to the version 2406 (Build 17726.20126) the add-ins bundle.js was working completely fine with references to Intl package and its standard functions (the same add-in bundle still works fine on some of the older Outlook versions across our client desktops).
When using the latest version on the current-channel: references to Intl in the Add-In bundle (JavaScript only runtime) throws errors like this to the office logs:
Verbose Runtime [Console] [Log] [ReferenceError: Intl is not defined]Has there been changes to Intl package / availability of it lately? Is this a bug? Is this a dropped support? Or have we used some unsupported package previously?
We really would not like to budle Intl functionality to the extension code base because this issue impacts events executed on "JavaScript runtime only" on Outlook Classic and not the browser based platforms like OWA/new Outlook/Classic Outlook's side panel.
Steps to reproduce
Happy to share our add-in manifest.xml privately to test between different versions if desired, but thought this can be first clarified if the support should be there in the first place before digging into deeper.
Link to live example(s)
Provide additional details
Context
Our clients are mostly in Enterprise semi-annual, or Enterprise monthly channels so the impact is quite contained still, but it looks like the problem might get out of hand if the Intl support is purposefully dropped from the launch events.
Useful logs
Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.