New issue
Advanced search Search tips

Issue 670796 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

testharnessreport.js: output_document option not supported

Project Member Reported by szager@chromium.org, Dec 2 2016

Issue description

Upstream testharness.js supports an output_document option to setup(), in the event that you want to generate test status output in a different document from the one that runs the tests:

https://github.com/w3c/testharness.js/blob/master/docs/api.md#setup

However, our internal testharnessreport.js does not honor output_document, and just uses 'document' willy-nilly.

This is making it hard for me to write/port IntersectionObserver tests that  run in an iframe (which is the most important use case).
 
Cc: tkent@chromium.org jeffcarp@chromium.org qyears...@chromium.org rbyers@chromium.org
Labels: Hotlist-PredictabilityInfra
Owner: foolip@chromium.org
Status: Assigned (was: Untriaged)
Interesting.  foolip et. al: WDYT?
Interesting, do we have an internal version of testharnessreport.js living in imported/wpt that shouldn't be upstreamed to WPT?
upstream testharnessreport.js is intentionally left blank; it's just a placeholder for users like us to insert our hooks.
Got it, I'll make a bug to exclude that file from any exports.
Owner: szager@chromium.org
Status: Fixed (was: Assigned)
This was fixed in #2 and jeffcarp has filed  issue 671890 , so closing this.
Components: Blink>Infra>Predictability
Labels: -Hotlist-PredictabilityInfra
Components: -Blink>Infra
Components: Blink>Infra>Ecosystem
Components: -Blink>Infra>Predictability

Sign in to add a comment