Publish packages 🚀#969
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@quilted/threads@4.1.0
Minor Changes
#968
b17b028Thanks @lemonmade! -ThreadWindow'stargetOriginoption now also validates theoriginof incoming messages, and gained an'ancestor'mode.Previously
targetOriginonly set the origin for outgoingpostMessage()calls; inbound messages were accepted from any origin as long as they came from the expected window. It is now also used to reject messages whoseorigindoes not match, so a concretetargetOriginauthenticates both directions:The default remains
'*'(post to, and accept from, any origin), so existing behaviour is unchanged.You can also pass
targetOrigin: 'ancestor'to pin to the origin that framed the current window — read fromlocation.ancestorOrigins, falling back to the origin of the first received message on platforms without that API (e.g. Firefox), buffering outgoing messages until it is known. This is convenient inside aniframethat trusts its embedder but doesn't know the embedder's origin ahead of time: