W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > January to March 2014

Re: Controlling the browser environment/settings

From: David Burns <dburns@mozilla.com>
Date: Thu, 27 Mar 2014 15:33:07 +0000
Message-ID: <533444B3.2020205@mozilla.com>
To: James Graham <james@hoppipolla.co.uk>, "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>, "public-test-infra@w3.org" <public-test-infra@w3.org>
I have never tried it but I fully expect WebDriver to get a little upset 
by this (note I havent tried this). With WebDriver, from the OSS world 
and from Marionette, we expect there to be a network so that we can 
speak to the browser (with FirefoxDriver we need to communicate with 
httpd.js and with Marionette we go in via the remote debugger).


On 27/03/2014 12:24, James Graham wrote:
> For testing certain kinds of things it is very useful to be able to 
> put the browser into unusual modes which cannot be activated via 
> normal web apis. The particular example that I have in mind is offline 
> mode; being able to simulate the browser disconnecting and 
> reconnecting to the network is very useful for testing technologies 
> such as AppCache / Service Worker and web applications using these 
> features to provide offline support.
> Since this is something that can't be provided as a DOM API (except in 
> some hypothetical debug mode) and that is very useful both for testing 
> browsers and for testing web applications, it seems like WebDriver 
> would be the natural home for such a feature. Is it already supported 
> in some way that I missed? If not is it something that could be added?
Received on Thursday, 27 March 2014 15:33:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:09:49 UTC