[py]: test enabling fedcm tests for chrome #16118
Draft
+0
−1
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
|
As per https://issues.chromium.org/issues/425801332 this should be resolved once Chrome 140 is out. Manual test against chrome canary verifies this. |
|
Nice. We might want to setup CI so we can test against beta releases of Chrome (I think Ruby bindings do this). I'm not sure if it would add too much noise... but it would be cool to see breaking changes and fixes in upcoming releases so we can be ready when they hit the stable channel. |
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.
🔗 Related Issues
💥 What does this PR do?
Enable FedCM tests for chrome
🔧 Implementation Notes
💡 Additional Considerations
🔄 Types of changes