When the slideshow has started, goToById doesn't change the current slide for a taskpane add-in on web.
This is a resubmission of #875 which @donlvMSFT closed despite me providing a minimal working reproduction repository and him confirming the repro and filing internal bug 3809617. He provided a content add-in manifest which appears to work as expected, but this issue is related to a taskpane add-in. He didn't provide the full code to me so I cannot investigate further myself. In any case I have identified a bug, provided detailed information for you to diagnose, and you have confirmed it so I'm pretty frustrated that the issue was closed anyway. This is now holding up a store submission because my functionality doesn't work on web.
Possibly related: #35
During presenting mode goToById should change the currently visible slide.
Nothing happens
Office.context.document.goToByIdAsync(Office.Index.Next,Office.GoToType.Index, () => {}) from an add-in or DevTools console.See https://github.com/gordonmleigh/repro-officejs-875.
I'm trying to control the slideshow from the add-in, which works on desktop.
Hi @gordonmleigh , sorry for that the original issue #875 is closed by accident, probably because the tag is not proper set. Really sorry for that.
We already filed the bug 3809617 tracking this, and will come back if there is any progress.
@donlvMSFT we've had a submission to the store rejected because the functionality doesn't work in Office online. Have you any idea what the timescales will be on this fix?
Do we need to wait until this bug is fixed by your team before we can go ahead, or can we resubmit quoting your internal bug ID in the meantime?
@gordonmleigh I am sorry for the inconvenience to bring to you. I am afraid that the submission may not success if the functionality doesn't work. There is a bug #3809617 filed to track the issue. The bug fix process may can be accelerated if you provide some data on how big the impact is. You may can drop me an email ([email protected]) if the data is sensitive.
Most helpful comment
Hi @gordonmleigh , sorry for that the original issue #875 is closed by accident, probably because the tag is not proper set. Really sorry for that.
We already filed the bug 3809617 tracking this, and will come back if there is any progress.