Tony Jin

Hey @Carel155, the `setRequestCredentials` API introduced with v1.4.0 may solve your use case: https://aws.github.io/amazon-ivs-player-docs/1.4.0/web/interfaces/player.html#setrequestcredentials

@nightpool this should be resolved with v1.3.0, please let us know if you still see this. https://docs.aws.amazon.com/ivs/latest/userguide/release-notes.html

Sorry, re-opening this issue. I see that v1.3.0 doesn't resolve the issue in your demo, and neither does v1.4.1, which is currently out.

We're focusing our development on the Javascript Preview SDK, which will power the New Box View. More features will be added as time goes on. The biggest benefit of New...

Yup! Functional parity with viewer.js is on our backlog, but I don't have a timeline to share right now.

Could you provide the original file @saiena? We're also currently seeing some issues with Chrome 49 and viewer.js that are resolved in later versions of Chrome.

Both files work fine in Chrome Canary (51.0.2693.2) with the Crocodoc viewer. I highly suspect these files are affected by the same class of regressions we've seen with other documents...

You could try setting enableTextSelection to false in Viewer Config, not sure if that's what you're referring to.

@bpartridge Do you see issues with Chrome Beta or Canary? On my end, I saw most of these issues resolved with Chrome 51, which should be stable on 5/31 according...

Thanks for the request, we've considered batch operations before and will keep evaluating it for our roadmap.