On 28 Jul 2020, at 11:56, Michael Richardson wrote:
Benjamin Kaduk <kaduk@xxxxxxx> wrote:
>> On Mon, Jul 27, 2020 at 7:53 PM Ben Campbell <ben@xxxxxxxxxxx>
wrote:
>>
>> > Fair point. I guess I’m compartmentalizing the blame.
>> >
>>
>> Well, before we apportion the blame it would be useful to know
what the
>> source of the problem is. Do we have bug reports that describe
the defects
>> that are causing problems?
> The documentation at
>
https://www.ietf.org/media/documents/Documentation-Meetecho-IETF.pdf
> already refers to some limitations about Safari (only allows
sharing whole
> screen, not individual windows). I'm not sure whether there
were any other
> issues people were seeing.
My understanding of the problem on MacOS (which I don't use), for all
the
browsers, is that if you share a single application, that you wind up
sharing
the File/Edit/etc. menu, so effectively you always transmit a
full-screen
sized bit map, but maybe with a lot of blank.
But, with Chrome, you can share a single tab or single Chrome window,
so you
avoid this.
But, maybe I do not understand.
When I did a bit of testing on this, it turns out that the documentation
above is not quite accurate:
When using Meetecho with Safari, if you have multiple screens, only one
screen will be shared (not the entire screen real estate), but it shares
the currently active screen and does not give you a choice of screens to
share. That means if you want to share monitor #1 and put your Meetecho
window on monitor #2, you first move the Meetecho window to monitor #1,
start up screen sharing, and then move the Meetecho window to monitor
#2. Not ideal, but not too complicated. As the documentation says, in
other browsers, you're able to share particular windows, which makes the
process much easier.
pr
--
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
