search

OfficeDev / office-js

A repo and NPM package for Office.js, corresponding to a copy of what gets published to the official "evergreen" Office.js CDN, at https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
https://learn.microsoft.com/javascript/api/overview
Other
667 stars 94 forks source link

With reading pane hidden, spam addin hangs when reporting emails. #4560

Open glr0221 opened 2 months ago

glr0221 commented 2 months ago

Provide required information needed to triage your issue

With reading pane or preview off, spam addin hangs when reporting emails.

Your Environment

Expected behavior

Spam addin should be able to process emails even if preview pane is not shown or even if the email is not opened. This is the behavior we see in the classic-look outlook.

Current behavior

This is a bug. Spam addin hangs when processing an email that is not being previewed nor opened.

Steps to reproduce

  1. Download the sample code in : https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/outlook-spam-reporting
  2. Sideload manifest.xml
  3. Open Windows Outlook in new look outlook.
  4. Ensure that the preview/reading pane is set to 'Hide Reading Pane'.
  5. Select/Highlight/Check an email without opening it.
  6. Click on the spam addin button.
  7. Spam addin hangs.

Link to live example(s)

NA

Provide additional details

NA

Context

Very bad user experience for all end users. Classic outlook works great. New look outlook causes a hang issue.

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.

glr0221 commented 2 months ago

@exextoc this is reproducible in the browser. Upon my investigation, it seems that the code is stuck in Office.onReady(). I hope this helps. Thanks.

mobisw-msft commented 2 months ago

@glr0221 ,

Thank you for reporting this issue regarding the Spam add-in hanging on Hidden reading pane. We have added this bug to our backlog. However, we have no timelines to share at this point.

Internal Tracking ID: 4655676