feat: Long-term fix for cross-origin iFrames
Our previous LTI Component XBlock provides an option to "View resource in a New Window", which uses JS to launch a new window/tab. These capabilities were removed in Chrome v92. Chrome provided a temporary work-around which we now use in production. But we now need to design and implement a longer term fix. These issues have since migrated to Safari, and “before other browsers implement this change, which they have indicated that they will” we need to resolve this issue with something other than band-aids. Google Chrome’s and Safari’s move, however, is aligned with making iFrame technology more secure, which we can read as a signal that the industry will continue to advance in the direction of iFrames. This fix replaces the browser dialog with a custom javascript one.
#204.
What's Changed
- build: latest pylintrc from edx-lint by @nedbat in #199
- Python Requirements Update by @edx-requirements-bot in #198
- Python Requirements Update by @edx-requirements-bot in #200
- Python Requirements Update by @edx-requirements-bot in #202
- Python Requirements Update by @edx-requirements-bot in #203
- Python Requirements Update by @edx-requirements-bot in #205
- feat: advertise constraints in setup.py by @edx-requirements-bot in #206
- Python Requirements Update by @edx-requirements-bot in #208
- fix: Long-term fix for cross-origin iFrames by @connorhaugh in #204
- Standardize version number placement by @aht007 in #207
- docs: reflect changes in changelog and version by @connorhaugh in #209
New Contributors
- @connorhaugh made their first contribution in #204
- @aht007 made their first contribution in #207
Full Changelog: 3.1.0...3.1.1
