From 65f4ff51cbb45dbb4f239b5c0a88a3840e6d1f51 Mon Sep 17 00:00:00 2001
From: James Graham <james@hoppipolla.co.uk>
Date: Tue, 27 Jul 2021 20:35:49 +0100
Subject: [PATCH] RemoteContext object for testdriver.

This provides convenient access to the testdriver API bound to a different context.
---
 rfcs/testdriver_remote_context.md | 38 +++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 rfcs/testdriver_remote_context.md

diff --git a/rfcs/testdriver_remote_context.md b/rfcs/testdriver_remote_context.md
new file mode 100644
index 00000000..b6d3a4ef
--- /dev/null
+++ b/rfcs/testdriver_remote_context.md
@@ -0,0 +1,38 @@
+# RFC 91: `testdriver` RemoteContext object
+
+## Summary
+
+Provide `test_driver.RemoteContext` which is a convenient wrapper over
+directing commands to another browsing context.
+
+## Details
+
+Lots of testdriver functions take `context` as a final parameter. This
+is used when the test file wants to cause some action to happen in a
+different browsing context
+e.g. `test_driver.delete_all_cookies(context)`. If a context is being
+used repeatedly it's tedious and error-prone to have to keep supplying
+the context id explictly. Instead it's more convenient to work with an
+object with the context id already correctly bound.
+
+`RemoteContext` is an object that wraps the part of the `test_driver` API
+which takes a `context` parameter, and calls the underlying API with
+a context set at object creation:
+
+```
+let ctx = new test_driver.RemoteContext(frames[0]);
+ctx.delete_all_cookies()
+```
+
+## Risks
+
+As proposed creating the context might be quite verbose. Maybe
+`RemoteContext` should be on window instead (or have a shorter name).
+
+This is more code to maintain without adding much additional
+functionality.
+
+## References
+
+[PR 29803](https://github.com/web-platform-tests/wpt/pull/29803)
+contains a prototype implementation of this.