Philzen

@segunadebayo @tioluwani94 @estheragbaje @cschroeter would it be possible get a 2.8.3 release anytime soon? With the last 2.x release now almost 9 months old, there are a couple of fixes...

> v2.9.1 is now released @segunadebayo Thanks! This also seems to package a couple of things differently when compared to 2.8.2 (i.e. `@chakra-ui/focus-lock` and heaps of other imports have been...

Thanks again @segunadebayo. On reconsideration, i believe this issue should be reopened as it still exists – the new releases only re-enable the workaround, while the behavior of `isLoading` making...

@jacebenson This should be a problem of the past with storybook now using vite. I just tried and could not reproduce it using storybook-vite – any change to the mock...

This is also something we bumped into. We took the track from the `participant.videoTrackPublications` map, then used `dimensions.width` and `dimensions.height` to display the streams' dimensions in our application (as we...

> The best way I've found to get actual dimensions of the currently subscribed video is to read from `myAttachedVideoElement.videoWidth` + `.videoHeight`. There's also a `resize` event on video elements...

> The `dimensions` on the publication refer to the original publication dimensions of a track that a user is publishing, not the dimensions of what the participant is currently subscribed...

Based on @lukasIO's hint, this is what we're now doing as a workaround until this is fixed – works like a charm: ```tsx const getVideoDimensions = (videoPub: TrackPublication) => {...

Regarding your first issue: as you haven't specified any library it defaults to `okhttp-gson`, which – as the name suggests – currently only supports GSON (a request to add Jackson...

Any objections merging this?