This message was deleted.

Code that enables screen share:

void _activateScreenShareDesktop(BuildContext context) async {
    try {
      if (participant == null) return;

      <http://_log.info|_log.info>('_activateScreenShareDesktop()');
      DesktopCapturerSource? source = await showDialog<DesktopCapturerSource>(
        context: context,
        builder: (context) => ScreenSelectDialog(),
      );
      if (source == null) {
        _log.warning('_enableScreenShare(): cancelled screenshare. No Source selected.');
      } else {
        <http://_log.info|_log.info>('_enableScreenShare(): DesktopCapturerSource: ${source.id}');
        var options = room.roomOptions.defaultScreenShareCaptureOptions.copyWith(
          sourceId: source.id,
        );
        var track = await LocalVideoTrack.createScreenShareTrack(options);

        await participant!.publishVideoTrack(track);
      }
    } catch (e) {
      _log.severe('_activateScreenShareDesktop(): ${e.toString}', e);
      rethrow;
    }
  }

In the two images you see the actual full window and then what's visible in-app in the screen share.

cc @freezing-lifeguard-43174

@boundless-salesclerk-13461 Do you think the issue is on the capturing side or could it be rendering? I wonder if it's doing an aspect-fill instead of aspect-fit. (which still could be an SDK bug). are you able to see what it shows with the JS sample?

@dry-elephant-14928 am investigating and comparing with example app

thanks for confirming TPF! I think we should really just make this the default here! If the user isn't setting anything, we shouldn't crop screenshare