X Tutup
Skip to content

avm1: Make XmlSocket.connect(null) behave like connect()#23000

Open
adrian17 wants to merge 1 commit intoruffle-rs:masterfrom
adrian17:avm1-xmlsocket-fix-connect-fallback
Open

avm1: Make XmlSocket.connect(null) behave like connect()#23000
adrian17 wants to merge 1 commit intoruffle-rs:masterfrom
adrian17:avm1-xmlsocket-fix-connect-fallback

Conversation

@adrian17
Copy link
Collaborator

@adrian17 adrian17 commented Feb 10, 2026

Fixes #22995 .

Also added logging to a failure case (avm2 implementation has the same logging), but didn't change the behavior.

@kjarosh
Copy link
Member

kjarosh commented Feb 10, 2026

Can we add a test for it?

@kjarosh kjarosh added A-avm1 Area: AVM1 (ActionScript 1 & 2) T-fix Type: Bug fix (in something that's supposed to work already) labels Feb 10, 2026
@ChrisCPI
Copy link
Contributor

ChrisCPI commented Feb 10, 2026

Does this also fix when undefined is provided instead of null?

Edit: Assuming yes because of the line: let host = if matches!(host, Value::Null | Value::Undefined)

@adrian17
Copy link
Collaborator Author

Can we add a test for it?

I don't really know how to :c

@adrian17
Copy link
Collaborator Author

@kjarosh do you consider the lack of a test to be blocking?

@kjarosh
Copy link
Member

kjarosh commented Feb 11, 2026

Sorry about the delay, I planned to take a look and craft a simple test. Not having a test can introduce regressions in the future, I don't think it's blocking though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-avm1 Area: AVM1 (ActionScript 1 & 2) T-fix Type: Bug fix (in something that's supposed to work already)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue when providing null for host in XMLSocket.connect()

3 participants

X Tutup