Closed Bug 1400473 Opened 7 years ago Closed 7 years ago

Update talos test tpaint.html to comply with new toplevel data: URI navigation policy

Categories

(Core :: DOM: Security, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla57
Tracking Status
firefox57 --- fixed

People

(Reporter: ckerschb, Assigned: ckerschb)

References

Details

(Whiteboard: [domsecurity-active])

Attachments

(1 file, 1 obsolete file)

      No description provided.
Assignee: nobody → ckerschb
Blocks: 1380959
Status: NEW → ASSIGNED
Priority: -- → P1
Whiteboard: [domsecurity-active]
Now we are back to where we were for Bug 1393350, which then caused the performance regression and we changed the test back to using a data: URI within Bug 1393742.
Smaug, Joel, the pref |security.data_uri.block_toplevel_data_uri_navigations| blocks loading of the data: URI here [1]. We already had a similar problem within Bug 1393350, which we fixed by loading the data: URI from an external file. In turn, this change caused a performance regression so we changed it back to using a data: URI and a postmessage handler within Bug 1393742.

The problem here is that the pref "security.data_uri.block_toplevel_data_uri_navigations" blocks loading of the data: URI in the toplevel window entirely. Hence, I see two options:

a) We rewrite tpaint.html to load the data: URI from an external file and use the new perf number as the new baseline.
b) We somehow manage to explicitly set that pref before loading the test. I looked at other talos tests but couldn't really find a way to do that.

What do you think?

[1] https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/tests/tpaint/tpaint.html#78
Flags: needinfo?(jmaher)
Flags: needinfo?(bugs)
Attached patch bug_1400473_update_tpaint.patch (obsolete) — Splinter Review
I don't see a way to actually flip that pref :-(

Here is a patch for loading the data: URI from an external file in case we decide to go down that route and someone already wants to r+ that change.
I think for now setting the pref somehow sounds like the best option. Otherwise tpaint starts to measure different things.

But I'm not against a new file either. We just need to understand the baseline for the test result changes significantly.
I think this is up to jmaher.
Flags: needinfo?(jmaher)
Flags: needinfo?(bugs)
Joel, as discussed on IRC, it's best if we just flip the pref explicitly within testing/talos/talos/test.py. Thanks for your help with that!
Attachment #8908950 - Attachment is obsolete: true
Attachment #8909292 - Flags: review?(jmaher)
Comment on attachment 8909292 [details] [diff] [review]
bug_1400473_update_tpaint.patch

Review of attachment 8909292 [details] [diff] [review]:
-----------------------------------------------------------------

glad it is this simple!
Attachment #8909292 - Flags: review?(jmaher) → review+
Pushed by mozilla@christophkerschbaumer.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ff9e6251cd55
Update talos test tpaint.html to comply with new toplevel data: URI navigation policy. r=jmaher
https://hg.mozilla.org/mozilla-central/rev/ff9e6251cd55
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: