Skip to content
Test

Fix Safari reporting wrong initial track resolution (#898) #2270

Sign in to view logs

Fix Safari reporting wrong initial track resolution (#898)

Fix Safari reporting wrong initial track resolution (#898) #2270

Triggered via push October 23, 2023 17:37
@lukasIOlukasIO
pushed 40ccf2a
main
Status Success
Total duration 1m 50s
Artifacts –

test.yaml

on: push
test
1m 39s
test
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden
test: dist/livekit-client.umd.js#L1
ES2020 BigInt is forbidden