Closed Bug 1227260 Opened 4 years ago Closed 4 years ago

Control Centre prototype

Categories

(Firefox OS Graveyard :: Gaia::System::Browser Chrome, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
2.6 S4 - 1/1

People

(Reporter: benfrancis, Assigned: rakhavan)

Details

(Whiteboard: [systemsfe])

An architectural spike to explore the Control Centre feature and find the missing platform pieces.
Status: NEW → ASSIGNED
Target Milestone: --- → 2.6 S3 - 12/18
Target Milestone: 2.6 S3 - 12/18 → 2.6 S4 - 1/1
I started a branch [1] and began taking over the old pin the web dialog. I've got the dialog opening and showing the domain at the top and removed pin the web stuff from it. I've also renamed classes and functions. I made sure the related unit tests got updated, but still need to double check against integration tests.

I'm ready to start implementing the UI. The UI work is blocked by the platform needs (for the most part).

These platform items need to be turned into bugs:

 - Expose SSL Certificate information to Gaia
 - Expose Tracking Protection details to Gaia
 - Allow setting Tracking Protection for a browser iframe

Some ideas on how we could approach these:

 - Maybe exposing SSL and Tracking Protection information could done by adding details to the `mozbrowserlocationchange` event. maybe a new even is better.
 - Maybe setting tracking protection on a browser iframe could be done by setting a new `mozbrowsertrackingprotection` attribute on the browser iframe. This would let us turn is on by defualt using a global Tracking Protection setting.

Besides these platform needs, I'm ready to turn the outline I created into a bug tree and setup dependencies.

[1] https://github.com/jedireza/gaia/tree/control-panel-spike
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.