Skip to content

Display correct guidance text for device permission error on safari#2590

Merged
carocao-msft merged 19 commits intomainfrom
carocao/safariCallReadiness
Dec 15, 2022
Merged

Display correct guidance text for device permission error on safari#2590
carocao-msft merged 19 commits intomainfrom
carocao/safariCallReadiness

Conversation

@carocao-msft
Copy link
Copy Markdown
Contributor

What

Display correct guidance text for device permission error on safari

Why

https://skype.visualstudio.com/SPOOL/_workitems/edit/3086741

How Tested

Screenshot 2022-12-13 at 10 08 59 AM

Screenshot 2022-12-13 at 10 08 55 AM

Process & policy checklist

  • I have updated the project documentation to reflect my changes if necessary.
  • I have read the CONTRIBUTING documentation.

Is this a breaking change?

  • This change causes current functionality to break.

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 13, 2022

Chat bundle size is increased❗.

  • Current size: 5577063
  • Base size: 5575150
  • Diff size: 1913

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 13, 2022

Calling bundle size is increased❗.

  • Current size: 5483538
  • Base size: 5481071
  • Diff size: 2467

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 13, 2022

CallWithChat bundle size is increased❗.

  • Current size: 5871398
  • Base size: 5868931
  • Diff size: 2467

@github-actions
Copy link
Copy Markdown
Contributor

Comment thread packages/react-components/src/components/DevicePermissions/DomainPermissions.tsx Outdated
@github-actions
Copy link
Copy Markdown
Contributor

@carocao-msft carocao-msft changed the title Display correct guidance text for device permission error on safari Display correct guidance text for device permission error on safari [in progress] Dec 14, 2022
…2585)

* Add continue button to browserVersion UI

* update styles

* add new button logic to call adapter

* add logic to callWithChat

* fix handler logic

* fix styles

* Fix cc and build stable API

* remove console

* Change files

* Duplicate change files for beta release

* update strings

* update styles for strings

* update per comments

* update UI state naming

* build API

* fix test errors

* Update packages/react-composites CallComposite browser test snapshots

* Update packages/react-composites CallComposite browser test snapshots

* update styles

* Update packages/react-composites CallComposite browser test snapshots

* update styles

* Update packages/react-composites CallComposite browser test snapshots

* Add new tests

* Change files

* Duplicate change files for beta release

* Update packages/react-composites CallComposite browser test snapshots

* fix styles and storybook bug

* Update packages/react-composites CallComposite browser test snapshots

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
dmceachernmsft and others added 2 commits December 14, 2022 14:51
…fulCallClientState (#2593)

* update adapted selector function

* Change files

* Duplicate change files for beta release

* remove console
@carocao-msft carocao-msft changed the title Display correct guidance text for device permission error on safari [in progress] Display correct guidance text for device permission error on safari Dec 14, 2022
@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

Comment thread packages/react-components/src/components/DevicePermissions/DomainPermissions.tsx Outdated
@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

Comment thread packages/react-components/src/components/DevicePermissions/DomainPermissions.tsx Outdated
Comment thread packages/react-components/src/components/DevicePermissions/DomainPermissions.tsx Outdated
Comment thread packages/react-components/src/components/DevicePermissions/DomainPermissions.tsx Outdated
@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

/**
* Whether we are using safari browser or not
*/
isSafari?: boolean;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isSafari is OK, but if we ever needed to do something specific for firefox having a boolean makes it less extensible

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want to move the logic to callreadinessmodal and pass it down to domain permissions, we can only pass along a boolean. Earlier I had the logic inside domain permissions component so that when we need to do something for firefox it also works

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it we can only pass a boolean? We can do

const isSafari = _isSafari(environmentInfo);
<CameraAndMicrophoneDomainPermissions
  browser={isSafari ? 'safari' | 'other'}
/>

Copy link
Copy Markdown
Contributor Author

@carocao-msft carocao-msft Dec 15, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this way we are still limited when we need to do something specific for firefox, since 'other' includes chrome and firefox and edge. Should we have the browser type to be safari | firefox | chrome | other ? But then our logic here doesn't make sense browser={isSafari ? 'safari' | 'other'} since we are assigning chrome and firefox to other.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we need to do firefox we can then add it, but you're correct that other isn't so great, perhaps:
browserHint: 'safari' | 'unset'
?

Copy link
Copy Markdown
Member

@dmceachernmsft dmceachernmsft Dec 15, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I like the idea of spreading it out to define the major browsers explicitly so other refers to browsers like Brave, duckduckgo and so on. I'd argue Opera might be in there too but it is prominent enough in the world that Calling could want to support it in the distant future.

this would also give a vector to have the component know which browser its on in the future. (thinking of maybe that gif thing Mikhail mentioned this morning in the review)

Copy link
Copy Markdown
Member

@JamesBurnside JamesBurnside left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can iterate on the isSafari prop in future so not blocking for this PR, at GA we will likely get feedback from review boards to avoid the boolean - we can always update then - otherwise Pr looks great!

@carocao-msft carocao-msft merged commit b658baf into main Dec 15, 2022
@carocao-msft carocao-msft deleted the carocao/safariCallReadiness branch December 15, 2022 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants