Physical Web should prompt for Location/Bluetooth system setting if it is disabled |
||
Issue descriptionWe already check for Location and Bluetooth from our diagnostics page (chrome://physical-web), and we already prompt for Location permission for Chrome. However, it would be nice to point out to user when the system setting is disabled, and provide a link to help them enable it.
,
May 19 2016
We would only be able to do so on M+, and we'd have to ask for BT perms so that we could then prompt again regarding the setting. Would that be acceptable?
,
May 19 2016
Thats a good point. I think that would be fine, but lets ask Ani/Scott for product guidance.
,
May 20 2016
Could you explain what the full user flow would look like?
,
May 20 2016
1. User flips PW switch 2. We prompt for location permission 3. They accept 4. We prompt for BT permission 5. They accept 6. We prompt to turn on BT 7. They accept I think it might make more sense to just display status like the diagnostics page does. Then they could pick any one of the current issues and resolve it.
,
May 20 2016
Can we programatically turn on master BT, or can we only provide instructions to turn it on? Also, there is not BT permission now, right? I'd think the flow is the following: 1. User flips PW switch 2. We prompt for location permission 3. They accept 4. We educate how to turn on BT 5. They turn it on This flow feels fine to me -- user explicitly went to Privacy setting to flip the switch, so we should help them get to a state where they can use it.
,
May 23 2016
> Can we programatically turn on master BT, or can we only provide instructions to turn it on? By prompting them to turn it on, I mean, asking them if we may turn it on. > Also, there is not BT permission now, right? Right, thus steps 4 and 5 in my list. What I'm suggesting is we have some button that says "bluetooth status unknown...tap to resolve"...when they tap it we ask for permission and resolve the issue for them.
,
May 23 2016
>> What I'm suggesting is we have some button that says "bluetooth status unknown...tap to resolve"...when they tap it we ask for permission and resolve the issue for them. I was under the impression that we can't flip the master bluetooth switch for the, so the most amount of resolution we can do is telling them to turn it on. I still think we should do it, but wanted to clarify.
,
May 23 2016
> flip the master bluetooth switch for the Not sure how you were going to end that phrase there, but yes, once we have the BT permission, we can flip the BT switch for the user (although it will prompt them when we do so).
,
Jun 20 2016
Here is what the user sees before turning on PW. If we simply tell them to turn on BT, we could just better highlight that PW requires BT.
,
Jun 22 2016
Here is the new text that was proposed (and agreed to) by UI Review. This gets to Ani's point which is to just make it clear that Bluetooth has to be turned on. Please note the text is color highlighted just to show the changes. The change should stay all in the same color...
,
Jun 22 2016
Sorry, to clarify, this was the text reviewed for Bling (hence the slightly different UI
,
Jun 27 2016
+1 -- we should be consistent with the text on both platforms
,
Jan 9 2017
Do we still need to address something here?
,
Jan 18 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by mmo...@chromium.org
, May 16 2016Status: Assigned (was: Untriaged)