Create a test build for the updated about:privatebrowsing design




3 years ago
3 years ago


(Reporter: Paolo, Assigned: Paolo)


Dependency tree / graph
Bug Flags:
firefox-backlog +
qe-verify -

Firefox Tracking Flags

(firefox42 affected)


(Whiteboard: [fxprivacy] [campaign])


(1 attachment, 1 obsolete attachment)



3 years ago
We're going to do some preliminary user testing on the new design of the page shown when a new private browsing window is opened:

This bug is about putting together quickly a custom build for Windows that includes a static version of the above design. The following repository provides the helpers required for running the build more easily on Windows:

Some changes to preferences in the build will be required:
- Enable Tracking Protection UI
- Disable the first run page
Flags: firefox-backlog+


3 years ago
Flags: qe-verify-
Priority: P2 → P1
Whiteboard: [fxprivacy] [campaign]


3 years ago
Blocks: 1186170


3 years ago
No longer blocks: 1186170
Depends on: 1186170

Comment 1

3 years ago
Mockup can be found here

Comment 2

3 years ago
Created attachment 8640049 [details]
Tracking Protection Opening

Assets required to test the new mockup.

Comment 3

3 years ago
I've started a technical test build where I've incorporated the changes required for Nightly to run with a local profile at startup. If this works as expected, we might be able to provide just the EXE file instead of the ZIP on Windows. I'll let you know when the build is ready so we can validate the user testing installation flow internally. 

This build does not include the design changes yet, just a white header at the top of about:privatebrowsing to check that the build we're running is the one that includes the changes.

Matt, you mentioned disabling the first run page, but in my test Nightly didn't ask for anything special at startup (I've disabled the default browser check). Is there some preference I should change anyways?
Flags: needinfo?(MattN+bmo)

Comment 4

3 years ago
(In reply to bbell from comment #2)
> Assets required to test the new mockup.

The images in this archive don't include the "shield with webpage" icon that is visible in the mockup, which is actually essential to our test, as we'd like to see if this creates an association between the shield and Tracking Protection.

Can you provide a version of the assets that include this icon, if it's not too much trouble? I can also capture it from the mockup, but I may have to scale the image to match the resolution.

I also guess we're testing the "ON" version only, as the controls on the page won't be interactive.
Flags: needinfo?(bbell)

Comment 5

3 years ago
Updated since, confusingly, -Werror does not take effect in local binaries rebuilds.

Comment 6

3 years ago
I've created a technical Windows test build that runs automatically with a new profile from the temporary directory:

This should simplify the installation workflow, we'll have to update the instructions in the test to ask users just to download and execute the file in order to start Nightly.

I think Brian will incorporate the process I used to create this executable file into the current user testing helpers repository so the creation of this type of builds for Windows will be easier and more automated.

Note that in this version the first run page actually appears, I haven't looked into which preference to switch to prevent this yet.

Comment 7

3 years ago
Tomorrow I'll work on creating the build for the actual test we want to run.
(In reply to :Paolo Amadini from comment #3)
> Matt, you mentioned disabling the first run page, but in my test Nightly
> didn't ask for anything special at startup (I've disabled the default
> browser check). Is there some preference I should change anyways?

The pref startup.homepage_welcome_url should be set to the empty string. I see on MXR that it's the default for unofficial builds which I think try/local builds we use since again since fixes this year. Official Nightly has a URL specified.
Flags: needinfo?(MattN+bmo)

Comment 9

3 years ago
Created attachment 8640736 [details]
Tracking Protection Opening

I updated the assets to include the missing illustration and small check/attention icons. 

I was under the impression that we were testing with only a screenshot in the center. Sorry about that.
Attachment #8640049 - Attachment is obsolete: true
Flags: needinfo?(bbell)

Comment 10

3 years ago
I've created a tryserver build with the updated about:privatebrowsing page, and repackaged it in a self-extracting archive. Not all buttons and indicators on the page work as expected, but this is fine as participants are asked not to click on anything there. We'll include a version of the following instructions in the test:

We'll use a special test version of Firefox called Nightly. The
procedure to start this program changes depending on the browser and
operating system you're using, take the following as a general guide.

1. Click this link to start the download:

2. Click "Save File" when prompted (example screenshot:

3. If nothing happens when the download completes, click the Downloads
button (down arrow in the top right corner) and click the
"firefox-nightly-test-02.exe" item (example screenshot:

4. If you see a security warning, click "Run" to continue (example

5. Nightly should open automatically. When running the test, ensure you
are using the Nightly window, and not the window where
is open (the Nightly icon is a dark globe:

I haven't had a chance to pilot these instructions with non-technical users. Brian, Matt, do they sound correct to you?


3 years ago
Blocks: 1190427

Comment 11

3 years ago
This is completed and test results have been reviewed by Aislinn.
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.