Note: Pull requests which don't include the minimum details specified
in this template will probably be closed out-of-hand.
Issue Link or Description (the "what" and "why")
Closes #55
Implementation Plan
In general, no big changes are required for mobile views, the views are a number of miscellaneous tweaks away from "just working" on mobile.
One bigger change that will help a lot with a number of little quality improvements is using a production-grade dialog component. So the plan right now is
Added @headlessui/reactDialog component. On mobile the Intercom component will use this Dialog component instead of a standard div. On desktop using a Dialog gets a little bit weird for our use case because the Receiver window isn't a true dialog. It might make more sense to focus on something like a flyout use case, I'm not sure.
How the changeset was tested
A detailed list of cases which the author verified before requesting review.
Note: Pull requests which don't include the minimum details specified in this template will probably be closed out-of-hand.
Issue Link or Description (the "what" and "why")
Closes #55
Implementation Plan
In general, no big changes are required for mobile views, the views are a number of miscellaneous tweaks away from "just working" on mobile.
One bigger change that will help a lot with a number of little quality improvements is using a production-grade dialog component. So the plan right now is
Implementation Details (the "how")
@headlessui/reactDialogcomponent. On mobile theIntercomcomponent will use thisDialogcomponent instead of a standard div. On desktop using aDialoggets a little bit weird for our use case because the Receiver window isn't a true dialog. It might make more sense to focus on something like a flyout use case, I'm not sure.How the changeset was tested
A detailed list of cases which the author verified before requesting review.
Smoke tested using
relay.ccapp.Changes were verified on the following platforms: