Office-js: [Outlook] Changing a select drop down breaks pinning support

[splinter]

The ItemChanged event does not fire if a select dropdown value is changed.

Current Behavior

The ItemChanged event does not fire if a select drop value is changed.

Steps to Reproduce, or Live Example

1. Setup an ItemChanged handler
2. Ensure there is a Select dropdown in the view
3. Change the select drop down
4. The ItemChanged event does not fire.

I have attached a simple add-in in the gist below:

https://gist.github.com/splinter/0edeeee602ee5b691d799e7b292d6ded

Note: This behaviour is not present on systems with Chromium base Edge.

Context

The basic pinning use case of obtaining details on the currently selected mail is broken.

Your Environment

• Platform [PC desktop, Mac, iOS, Office Online]: Windows
• Host [Excel, Word, PowerPoint, etc.]: Outlook 2016 16.0.12624.20348 (32 bit)
• Office version number: 16.0.12624.20348 (32 bit)
• Operating System: Windows 10 Pro
• Browser (if using Office Online): Edge 44.18362.449.0

[exextoc]

The ItemChanged event is triggered when a different Outlook item is selected for viewing while the task pane is pinned. It will not fire when a dropdown is changed.

More information about event types can be found here

[splinter]

Hi @exextoc ,

First, I must apologize since I did not explain the issue properly.

The issue is not that the event is not fired when a select dropdown is changed.

The issue occurs when:

1. User enables pinning
2. User changes a select dropdown
3. User changes mail
4. No mail item changed event is fired

[exextoc]

Thanks for reporting this issue. We were able to repro this bug, and it has been put on our backlog. We unfortunately have no timelines to share at this point.

[jargil]

Thanks for reporting this. I've fixed this on Office builds 16.0.13001 and newer.

[mwickens]

Any chance there’s a work-around for this? Even once this is released, asking customers to upgrade in order to use our third-party add-in is not going to cut it.

[jargil]

@mwickens - this is fixed in 16.0.13001 and newer, are you still seeing this problem or are you in an older build? Is re-registering the events an option while waiting to get a newer Office build?

[mwickens]

Thanks for the quick reply. I was editing my comment when yours came in. As a third-party add-in, we can't ask all of our customers to upgrade (well, we can ask, but…). I'll look into re-registering the events.

[exextoc]

If you want to try the workaround of re-registering the events, ensure that you de-register (removeHandlerAsync) before re-registering (addHandlerAsync).

[mwickens]

Thanks, that worked!