Document Overview
| Feature/Product: | WebAPI - OS Idle API |
| Projected Feature Freeze Date: | (tbd) |
| Product Champions: | Bonnie Surender |
| Privacy Champions: | (the privacy Friend you're working with) |
| Security Contact: | Curtis Koenig |
| Document State: | [ON TRACK] needs more info |
Timeline:
| Architectural Overview: | In progress |
| Recommendation Meeting: | n/a |
| Review Complete ETA: | tbd |
Architecture
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described.
The main objective of this feature/product is: to inform general web content within tabs and windows of the user's idle and active state.
Design Documents: https://bugzilla.mozilla.org/show_bug.cgi?id=715041#c21
Components
Describe any major components in the system and how they interact. Also include any third-party APIs (those Mozilla does not control) and what type of data is sent or received via those APIs.
- User
- Web browser/Firefox
- Websites
- Websites loaded onto the browser tab within the browswer window or the window itself.
Websites
- Websites loaded onto a web browser.
- Ensure that maliscious websites do not have direct access to identify whether the user is idle or not.
Stored Data:
There is no stored data.
| What | Where |
|---|---|
| None | None |
Web broswer/ Firefox Component
- When the user stops using the device, i.e. becomes 'idle' the web browser is notified.
- When the user starts using the device again, i.e. becomes 'active' or comes 'back' the browswer is notified.
- The user 'idle' and 'back' status is platform specific.
- On platforms that do NOT support obtaining system idle time, if the user stops using the web browswer but continues to use another application currently executing on the device then the web browser is specifically notified that the user is idle despite the fact that the user is using another application. E.g. Linux, Android.
- The web browswer is notified that the user is 'active'/'back' only when the user specifically interacts with the web browser.
- On platforms that do support obtaining system idle time such as Windows, the web browswer is notified of user idle status only when the user is completely away from the device.
- The web browser is notified that the user is 'active'/ 'back' as soon as the user interacts with any application executing on the device. The user does not need to be directly interfacing with the web browser.
Stored Data:
There is no stored data.
| What | Where |
|---|---|
| None | None |
Communication with Places
| Direction | Message | Data | Notes |
|---|---|---|---|
| In: | 100 most-visited sites | List of URLs and titles |
User Data Risk Minimization
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.
Alignment with Privacy Operating Principles
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.
See Also: Privacy/Roadmap_2011#Operating_Principles:
Principle: Transparency / No Surprises
(How the feature addresses this)
Recommendations: (what can be improved)
Principle: Real Choice
Recommendations:
Principle: Sensible Defaults
Recommendations:
Principle: Limited Data
Recommendations:
Follow-up Tasks and tracking
| What | Who | Bug | Details |
|---|---|---|---|
| [NEW] Initial Overview Discussion | Bonnie Surender, Jonas Sicking | Meeting time TBD |