Before showing a screen, write down who should see it and what they need to see. That is our proposed exercise for this March 19, 2017 retrospective, prompted by Mozilla’s Firefox 52 release notes. Mozilla described a preview for screen sharing and removed the requirement for a whitelisted domain. The useful question for a presenter is narrower than whether sharing is available: does the view being offered match the material intended for this audience? [firefox52]

Google’s March 9 description of Hangouts Meet supplied a separate reason to consider the whole visible surface: it described presenting in full screen. Put that description on its own worksheet row rather than borrowing the Firefox preview claim. Neither announcement establishes that Meet uses Mozilla’s preview or that Firefox 52 supports Meet. For a proposed presentation, record the application and intended screen content, then leave preview availability marked unknown until it can be checked in that setup. [hangouts][firefox52]

Make the worksheet concrete: audience, intended visible surface, preview available or unknown, unrelated material to close, and a stop-or-verify decision. For a hypothetical volunteer briefing, the intended surface might be a delivery schedule; a separate personal message would belong on the close-before-sharing list. This is a preparation example, not an account of an exposure. Where a preview is available, compare it with the written scope. Where scope remains uncertain, pause and verify before presenting rather than filling the blank with an assumption. [firefox52][hangouts]

Keep this visual check distinct from less visible tracking questions. Mozilla also said it removed the Battery Status API with the aim of reducing tracker fingerprinting. That change concerns a different disclosure surface, not a preview of what meeting participants would see. A worksheet can organize a presenter’s choices without measuring fingerprinting or proving privacy. Its proposed endpoint is specific: an audience and screen scope the presenter has checked, or a decision to stop while an unknown is resolved. [firefox52]

Source documents

  1. Firefox 52.0 release noteshttps://www.firefox.com/en-US/firefox/52.0/releasenotes/?redirect_source=mozilla-org
  2. Meet the new enterprise-focused Hangoutshttps://blog.google/products-and-platforms/products/workspace/meet-the-new-enterprise-focused-hangouts/