+++ This bug was initially created as a clone of Bug #737153 +++ https://github.com/mozilla-b2g/gaia/issues/2333 The lastest status bar spec show that we need to show a "USB Message Storage" icon whenever the phone is being accessed by the computer. We have no such DOM API currently. (what we have right now is just a mozSettings key that can disable/enable the feature)
blocking-basecamp: --- → ?
Is this needed for v1?
Summary: Unable to probe status of USB Message Storage → Unable to probe status of USB Mass Storage
Leaving in the nom list for now until we determine if this is a V1 requirement or not.
Whiteboard: [soft][blocked-on-product] → [soft][blocked-on-input]
(In reply to Dietrich Ayala (:dietrich) from comment #2) > Leaving in the nom list for now until we determine if this is a V1 > requirement or not. It's already blocking-basecamp+ on Gaia issue.
It's not a requirement from UX point of view. Let's get Security input from Lucas and Antonio. FWIW, here is what the Permissions Matrix (https://docs.google.com/spreadsheet/ccc?key=0Akyz_Bqjgf5pdENVekxYRjBTX0dCXzItMnRyUU1RQ0E#gid=0) says, under "Visual indicators": Requires Visual Indicator: DeviceStorage API: No WebUSB: Yes
Lucas, pinging you belatedly for input here.
Note that not solving this bug for v1 means we are not going to implement System Overlay of the same indication https://github.com/mozilla-b2g/gaia/issues/2563
We aren't implementing webUSB for anything other than certified apps ATM which I think means this particular indicator is not a blocker for basecamp.
USB Mass Storage has nothing to do with WebUSB.
> USB Mass Storage has nothing to do with WebUSB. Sorry, that was probably result of me clouding issue. I think we're all on same page: * Current Status Bar indicator represents USB Mass Storage status. * We do not have a WebUSB status bar permissions indicator. * We can revist in future versions, once we open API to non-certified apps. My only concern is how we're going to visually differentiate USB Mass Storage vs WebUSB indicators in future. "Dear Future Josh, sorry for making you deal with this. Signed, Younger You."
Bug 784684 is being filed as duplicate of this one. The discussion and blocking status is here but the patch is there, so I am not sure which one to close...
I'm fine with pushing this off for V1, we just need Lucas' input on any security requirement around this.
blocking-basecamp: - → ?
blocking-kilimanjaro: ? → ---
See comment 10.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 784684
Seems like something we wouldn't want to regress.
blocking-basecamp: ? → +
I don't think its a security requirement. It might be a usability requirement insofar that when plugged in & mounted we should remind the user of that fact so they don't disconnect the cable w/o ejecting/dismounting, otherwise data corruption can result.
You need to log in before you can comment on or make changes to this bug.