- From: Philip Jägenstedt <notifications@github.com>
- Date: Mon, 16 Jul 2018 06:13:10 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 16 July 2018 13:13:39 UTC
@kereliuk, is there a tracking bug for implementing this in ChromeDriver? And in testdriver.js? If https://w3c.github.io/permissions/#set-permission-command has enough leeway to allow for the behavior that Safari has, then what we could do in testdriver.js is just to not allow use of the API except in top-level frames, so that tests can't depend on such differences. That'd be enough to unblock almost all getUserMedia and WebRTC tests, I'd bet. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/181#issuecomment-405242784
Received on Monday, 16 July 2018 13:13:39 UTC