Update WebViewer from iframe to "Web Component"
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
#### Description
Apryse released a change to Web Viewer - “Starting in 10.2 you can choose to instantiate WebViewer using a Web Component instead of an iframe.”
1. We might want to look into if the benefits of switching to “Web Component” sooner rather than later are worth it for us now.
2. Even if they’re not this is going to be relevant as they’re going to deprecate iframe eventually - from the bottom of the article:
“The default constructor will continue to use an iframe, but we recommend you start testing your application with the Web Component to ensure a smooth transition when we deprecate the iframe constructor in a future release.”
https://docs.apryse.com/documentation/web/guides/web-component-vs-iframe/#web-component:-the-reusable-powerhouses
#### Dependencies
#### DOD
- [ ] WebViewer is initialized as a Web Component
Contributor guide
Research direction
Read the linked Apryse Web Component versus iframe documentation, then locate the current WebViewer initialization entry point in the repository. Confirm the integration requirements and update the initialization so WebViewer uses a Web Component; done means the WebViewer is initialized as a Web Component.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100