Releases: ryanseddon/react-frame-component
v5.2.7
What's Changed
- fix: update FrameContextProps to use Document by @JamesSingleton in #244
- fix: call createPortal() on null tartget by @deathemperor in #255
New Contributors
- @JamesSingleton made their first contribution in #244
- @deathemperor made their first contribution in #255
Full Changelog: v5.2.6...v5.2.7
Contributors
Assets 2
v5.2.6
v5.2.5
Note: Please use 5.2.4, this version has a bug and will be superseded when a fix is rolled out. See #234
This release uses DOMContentLoaded as a better strategy over onload when more complex intitialContent payloads are provided.
This also accounts for timing issues and uses setInterval to account for cold cache timing issues on resource intensive frames.
v5.2.4
- fix: change default export away from React.Component (#227) e4cd1ca
- Bump shell-quote from 1.6.1 to 1.7.4 (#233) d5c25a3
- Bump decode-uri-component from 0.2.0 to 0.2.2 (#232) bb2c04e
- Bump engine.io from 6.2.0 to 6.2.1 (#231) d5235ba
- Bump socket.io-parser from 4.0.4 to 4.0.5 (#230) 73f0fb5
- Bump minimatch and wallaby-webpack (#229) b841e81
- Bump css-what from 2.1.0 to 2.1.3 (#228) e725602
v5.2.3-alpha.0
Building on v5.2.2-alpha.1 if DOMContentLoaded never fires we fallback with a setInterval
- Fallback to setInterval if DOMContentLoaded fails 28584e8
v5.2.3
Add types to package
This adds types directly to the package. You'll no longer need to rely on @types/react-frame-component
Rely on DOMContentLoaded to avoid timing issues - take 2
Building on v5.2.2-alpha.0 to try removing forceUpdate, guarding against a double state update and re-introducing the onLoad attribute.
- Seems to still have issues on chrome for some apps trying something else ae128fd
Rely on DOMContentLoaded to avoid timing issues
This is a pre-release testing whether using DOMContentLoaded is a better strategy over onload when more complex intitialContent payloads are provided.
- Rely on DOMContentLoaded instead of onload 39262db