13:06:31 RRSAgent has joined #testing 13:06:31 logging to http://www.w3.org/2013/06/14-testing-irc 13:07:42 Meeting: WebDriver F2F, June 14th 2013 13:08:46 fisherii has joined #testing 13:09:08 AutomatedTester has joined #testing 13:10:18 Agenda: http://www.w3.org/wiki/WebDriver/2013-June-F2F 13:11:25 Chair: sstewart6 13:11:29 Scribe: wilhelm 13:11:39 RRSAgent, draft minutes 13:11:39 I have made the request to generate http://www.w3.org/2013/06/14-testing-minutes.html wilhelm 13:11:43 RRSAgent, make logs public 13:12:46 Topic: Test suite 13:12:54 Scribe: plh 13:13:14 JohnJansen has joined #testing 13:13:31 David: it was more working on it and writing tests 13:13:46 Present+ DavidBurns 13:13:48 John: not sure if this is the venue or email but I'd like to understand the end-to-end plan for it 13:13:53 Present+ plh 13:14:04 David: it's in mercurial 13:14:05 https://dvcs.w3.org/hg/webdriver-test 13:14:16 Present+ Wilhelm 13:14:29 David: we're trying to port the open source project tests 13:14:39 ... those have grown quite organically over the years 13:14:44 ... sort them, etc. 13:14:56 ... we're trying to move them across 13:15:10 ... there are parts when the tests and the spec diverge 13:15:14 ... like at TPAC 13:15:29 ... but we think the spec is correct and need to fix the tests 13:15:39 Simon: we're taking the tests andmaking sure they map to the spec 13:16:12 ... once we're complete with the move, we can remove the tests in selenium 13:16:43 plh: license for the tests? 13:16:50 Simon: all Apache 2 tests 13:16:55 ... we're clean on that front 13:18:12 John: is there a structure for submission? 13:18:18 ... like in the CSS WG 13:18:55 Simon: correct, it would be better to have a holding 13:19:04 sstewart6 has joined #testing 13:21:50 plh: [trying to motivate the group to move to web-platform-tests github] 13:23:08 gdennis1 has joined #testing 13:23:59 kkania has joined #testing 13:24:20 https://github.com/w3c/web-platform-tests 13:24:56 chrisgao has joined #testing 13:28:21 All: looks like a compelling case 13:28:28 Simon: let's do it then 13:29:34 Resolution: webdriver tests will merge into web-platform-tests 13:30:30 Present+ MarcFisher 13:30:37 Present+ SimonStewart 13:30:39 Present+ KenKania 13:30:52 Present+ JohnJansen 13:30:54 Present + GregDennis 13:31:08 Present + ChrisGao 13:31:21 rrsagent, generate minutes 13:31:21 I have made the request to generate http://www.w3.org/2013/06/14-testing-minutes.html plh 13:31:54 Simon: we already covered language in the test suite (python) 13:32:10 Wilhelm: we should distribute chapters 13:32:19 (not been following, but it's not clear to me that webdriver tests are much like the other tests there, or if they have the same license) 13:32:29 Simon: will look 9, 10, 11 13:32:34 ... reading element state and executing JS 13:32:38 (although there are ofc adcvantages e.g. you get free documentation) 13:32:44 Wilhelm: I'll do 16 screenshots 13:33:13 David: I'll do 10 and 17 13:33:18 Simon: I'll do 9 and 11 13:33:59 David: I'll do 14 as well 13:34:28 https://dvcs.w3.org/hg/webdriver/raw-file/tip/webdriver-spec.html 13:34:38 (confusing about the spec version :) 13:34:43 s/sing/sion/ 13:34:51 Ken: I'll do 5 and 6 13:34:58 John: I'll do 2 and 3 13:36:18 Chris: I'll do 15 13:36:41 ACTION: Simon to figure testing for chapters 9 and 11 13:37:01 ACTION: David to figure testing for chapters 10, 14 and 17 13:37:11 ACTION: Chris to figure testing for chapters 2 and 3 13:37:20 ACTION: Wilhelm to figure testing for chapters 16 13:37:36 ACTION: Chris to figure testing for chapters 15 13:38:02 ACTION: Ken to figure testing for chapters 5 and 6 13:38:26 ACTION: John to figure out testing for chapter 1 13:38:55 s/Chris to figure testing for chapters 2 and/John to figure testing for chapters 2 and/ 13:39:02 rrsagent, generate minutes 13:39:02 I have made the request to generate http://www.w3.org/2013/06/14-testing-minutes.html plh 13:39:38 ACTIOn: Simon to create the web-platform-tests directory and move tests there 13:40:32 Simon: we'll figure out the other chapters later 13:42:38 [figuring out the next agenda item] 13:43:35 Topic: SysApps 13:43:41 http://www.w3.org/wiki/System_Applications 13:43:51 David: those are related to OS APIs. we're doing testing with marionette 13:44:40 ... we have JS libraries for access to things, like contacts, set geolocation, etc. 13:45:20 ... we do tests for batteries, bluetooth, livemaps, etc. 13:46:02 ... not sure I don't think we need to worry about it. we didn't extend marionette for them, we use the execute script method 13:46:17 [Simon goes through the list of APIs] 13:46:30 David: in Firefox OS we have a browser within a browser 13:46:34 Simon: we must go deeper :) 13:46:44 David: everything is based in an iframe 13:46:58 ... we try to prevent cross browser contamination 13:47:18 ... chrome os is doing similar things 13:47:44 ... a lot of these have come pout of Mozilla while working on firefox os 13:47:57 Specs appear to be here: https://github.com/sysapps 13:47:57 ... they are certain OEM who see value in it, like Samsung 13:48:14 ... don't think there are a lot of difference 13:48:29 ... the webdriver is low enough and don't need tweaking 13:48:59 David: Marionette is the only I think I can use to test firefox os 13:49:21 ACTION: David to double check there is no need to extend WebDriver because of Firefox OS 13:49:45 Simon: it works because the OS is written in JS... 13:49:52 David: agree but others would be out of scope 13:49:54 Simon: ok 13:51:07 Topic: Security dialogs 13:51:25 driver.authtenticateAs(Credentials) 13:52:15 http://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/Alert.html#authenticateUsing(org.openqa.selenium.security.Credentials) 13:52:30 Simon: it is currently unimplemented 13:52:41 ... it's there only as a local end API at the moment 13:53:07 ... this isn't handling things like OpenID 13:53:20 ... you would just write that use normal primitive 13:53:30 ... we model all modal dialogs as an alter 13:53:42 s/alter/alert/ 13:54:05 John: this is targetting the security dialog but we didn't target modal dialogs yet, right? 13:54:12 Simon: it's in the wired protocol 13:54:18 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/alert_text 13:54:28 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/accept_alert 13:54:34 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/dismiss_alert 13:54:47 David: this is the open source wire protocol, not the google one 13:55:02 Simon: this will be migrated into the missing appendix 13:55:39 Simon: the way we handle dialog: we assume they all have the same level functionality: dismiss, cancel, send keys, get the text of the alter itself 13:55:59 ... make sure to fill a field, ie finding out what the prompt is about 13:56:18 ... because you're doing auth, you may do user/passwrd but there is a level of indirection 13:56:38 Simon: do we want to allow webdriver to access basic digest? or is it out of scope? 13:56:54 Wilhelm: right now, I'm sending keys to the browser 13:57:40 John: automating a security dialog is a threat imho. it needs to be detailed and complete. 13:58:00 ... doing something that sounds insecure wouldn't fly in the company 13:58:21 ... we might not do it even if the spec says we have to 13:59:11 ... the limitation here that wouldn't be able to use webdriver for auth 13:59:26 Wilhem: how can I auth my staging area? 13:59:31 John: would need to auth first 13:59:39 Soimon: but we can't connect to a running server 14:00:14 Simon: on services like sourcelabs, you don't even have access... 14:00:20 s/Soimon/Simon/ 14:00:45 s/sourcelabs/Sauce Labs/ 14:01:11 David: for marionette, it's in the nightly. we got it approved: you would need to pass a flag 14:01:40 ... for desktop, it's command line flag. this goes through a number of checks, including certain preferences 14:01:50 ... if one is missing, marionette doesn't start 14:02:05 ... ie you have to do several steps to put you in an insecure state 14:02:21 ... for mobile, it's going to be different 14:02:35 ... we'll visit that once we're ready for the general public 14:02:54 ... that's how we got through the security review 14:03:10 Simon: the command line turns the browser into something that is listening 14:03:28 David: you need to have a number of commands in order to activate it 14:03:39 ... you can't remote over a network 14:03:55 ... you would need to have an intermediairy on the remote machine 14:04:19 ... you can't speak to marionette over the network 14:04:33 ... could be overriden but require deep knowledge of preferences 14:05:02 ... of course, if you can do silly things 14:05:28 John: interesting approach even if 99.9% guarantee isn't enough 14:05:52 John: in order to be hacked you need to make 3 or 4 wrong decisions 14:05:54 David: correct 14:06:10 Ken: it's a similar approach in Chrome 14:06:34 ... for android, not sure how the options get passed 14:06:54 ... since we don't speak wire protocol in chrome, you need a separate binary 14:07:07 David: yes, we have a shime for the http protocol as well 14:07:20 s/ shime / shim / 14:08:17 David: preventing add-ons from switching on marionette was vital 14:08:51 ... those aren't allowed in the store. those get automatically flagged 14:09:32 ... if you don't go through the store, all bets are off 14:10:42 ... I can find the security discussion meeting... 14:11:35 Simon: if you've got an API for automated browser, spammer can use it. there are JS variables to detect webdriver was enabled. 14:11:47 ... should we agree on a fingerprint 14:11:53 John: seems like a must to me 14:12:08 ... otherwise webdriver will be used against captcha 14:12:55 https://bugzilla.mozilla.org/show_bug.cgi?id=870576 https://wiki.mozilla.org/Security/Reviews/MarionetteCLIAll 14:13:30 Simon: so, is our spec the right place to put that in and should it be the same in all browsers? 14:13:48 Simon: initially, I was doing security through obscurity... 14:14:04 John: the obscurity will get clear very quickly... 14:14:13 ... there has to be something else 14:14:38 Simon: if you set an attribute on a document, it can get overriden... 14:14:52 ... in the ideal world, you would set a header 14:15:11 ... and you would set an attribute that cannot overriden, like document.automated 14:15:22 ... but then you can take advantage of the scoping rule... 14:15:31 ... and substitute it 14:16:29 David: some large websites, like Amazon, do detect things like phantomjs already 14:16:38 Simon: I'm going to siuggest a header 14:16:49 John: we might learn from XHR/CORS 14:17:15 ... it's sort of a similar problem. the combination of header and attribute could do it 14:18:26 ... so we must have a fingerprint, with a header and an attribute, and do a security review 14:18:37 Simon: let's put a strawman in the spec and get review 14:19:08 ACTION: Simon to put a proposal in the spec around the security mechanism header and attribute 14:19:21 ACTION: All get their security teams to review Simon's proposal 14:19:46 ACTION: Wilhelm to ping the Web Security WG on Simon's proposal 14:20:20 John: we have non-modal notification, like saveAs, etc. 14:20:53 Simon: we didn't run into those yet, like geolocation. we just defaulted everything to a particular state 14:21:43 John: some dialogs have several states, like the activeX (no, never, yes once, yes always) 14:21:59 Simon: that's leading in extra capabilities in HTML5... 14:22:28 ... does user media use the same prompt as geoloc? are those consistent? 14:22:42 David: we're consistent 14:22:45 John: as we are 14:23:00 David: we call those door hangers 14:23:12 [David shows the design] 14:23:29 [one button with several options] 14:24:44 Simon: so, what do we do? provide an API to allow a capability? 14:24:57 ... we nuke the profile everytime in Chrome 14:25:10 ... so always share doesn't really matter 14:26:05 ... we could override switchTo, like switchTo the permission dialog and then use the existing command (dismiss, ok) 14:26:41 ... if you ignore the dialog, it will default to No 14:27:43 Wilhelm: when I test the geoloc spec as a browser vendr, I'd want the four options but that's only 5 orgs in the world 14:28:04 Simon: you can set a profile... 14:28:35 Simon: so we want to pick between the two accept states 14:28:42 Marc: really, it's all four 14:28:52 ... so it's its own alert object 14:29:13 ... if we change the wire protocol to allow an index for dialog... 14:29:46 Simon: so alert response is the end point? 14:29:51 All: yes 14:30:28 ACTION: Simon to change the wire protocol to add the alert response and could take 4 responses (yes, yes always, no, no, always) 14:30:32 John: what about ignore? 14:30:50 ... it's functionally equivalent to No 14:30:54 Wilhelm: so 4 options 14:31:07 John: I still would like to test this... 14:31:17 Marc: what about a string with predefined values? 14:31:34 Simon: I'm fine with mandating four and allow extensions 14:31:43 John: I still would like to have ignore 14:31:53 Ms2ger: I just showed a doorhanger :) 14:32:09 Simon: if we find it's useful, we can always come back to it in version 1.1 14:32:54 Simon: a few things to consider now: mocking locations, for image capture, mimicking the data 14:32:59 Marc: orientation... 14:33:51 Let's get coffee! 14:34:35 rrsagent, generate minutes 14:34:35 I have made the request to generate http://www.w3.org/2013/06/14-testing-minutes.html plh 15:01:42 chrisgao has joined #testing 15:01:52 Scribe: kkania 15:02:01 sstewart6 has joined #testing 15:02:07 Present+ SimonStewart 15:02:13 ok 15:03:34 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/location 15:04:07 Topic: handling location, camera, and other sensors 15:04:49 sstewart6: we have a number of options to do here 15:04:57 location, and media capture are probably the big 2 15:05:05 that would solve must individual use cases right now 15:05:20 JohnJansen: there is a slightly different question 15:07:22 sstewart6: it sounds like we should ask the people writing the specs to tell us what the best way to supply the mock data is 15:07:34 plh: there will be a cat picture 15:07:47 AutomatedTester: we can mock geolocation in js 15:08:10 kkania: the link above ponts at the wire protocol 15:08:48 sstewart6: I'm suggesting the two we should bake in now are geolocation and media capture 15:09:00 plh: what about device orientation? 15:09:09 sstewart6: and device orientation 15:09:17 sstewart6: so there's three we should bake 15:09:46 http://dev.w3.org/geo/api/spec-source-orientation.html 15:10:18 Orientation as it is now: https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/orientation 15:10:39 fisherii: portrait/landscape is different from device orientation 15:11:51 sstewart6: ok, let's go back to our original two, and allow users to specify whether it is upright or landscape 15:12:26 gdennis: there's portrait, landscape, portrait secondary, and landscape secondary 15:13:20 http://www.w3.org/TR/screen-orientation/ 15:13:53 fisherii: we should base orientation off of this spec 15:14:56 http://www.w3.org/TR/screen-orientation/#allowed-orientations 15:15:01 JohnJansen: I don't know if we support all 4 states 15:15:10 gdennis: that could be a no-op 15:15:27 fisherii: it could depend on the browser and device 15:15:39 fisherii: does the browser actually support that rotation, or device 15:15:45 but i think it should throw an exception if it is unsupported orientation 15:16:02 gdennis: i don't think it should be an exception, a user can put it in the orientation 15:16:11 fisherii: but screen orientation is not the same as the device orientation 15:16:29 AutomatedTester: so if we were to do all of this, telling the browser to change the orientation is going to be extremely difficult 15:16:41 so in the example of ff os, we can do it on the emulator, but not on real devices 15:17:01 AutomatedTester: we can't get the device to change orientation programmatically 15:17:04 sstewart6: well you could 15:17:19 sstewart6: there are things we'd like to say in the spec, even if the browser can't currently do it 15:17:39 AutomatedTester: can we expect the browsers to do this? 15:17:52 fisherii: well it's capability based, whether controlling the orientation is possible 15:18:06 if the device doesn't support it, the capability should return false 15:18:19 wilhelm: so what does happen if you do turn the device in question, does the orientation change 15:18:30 wilhelm: if the device can actually do it, we should be able to automate it 15:19:14 sstewart6: the language i want in the spec, is if you support a capability, you must provide the functionality 15:20:53 sstewart6: so are we happy with orientation, the four orientation values, for geolocation, latitude, longitude, altitidue 15:20:58 how long do these things stick for 15:21:01 fisherii: until change? 15:21:08 fisherii: rest of the session basically 15:21:10 sstewart6: ok 15:21:42 sstewart6: for media capture, we just allow people to upload a screenshot or something? 15:21:54 AutomatedTester: that's interesting, since you can do video and stuff 15:22:00 AutomatedTester: for webrtc, that's the biggest use case 15:22:06 fisherii: but the video could be a still picture 15:22:13 fisherii: and we don't do that well on dynamic things anyways 15:22:21 AutomatedTester: that's fine, as long as that is documented 15:22:33 http://www.w3.org/TR/2012/WD-html-media-capture-20120529/ 15:22:39 wilhelm: we could maybe make it simpler by not needing a picture from the user, but by just coloring the screen example 15:23:08 fisherii: camera is easy also, since it is only a single image 15:24:37 http://www.w3.org/TR/mediacapture-streams/ 15:24:57 fisherii: all of these are just file pickers on some sense 15:25:11 sstewart6: yes, they all upload a file of some sort, but how they capture is differnet 15:25:53 fisherii: so we don't have to do anything special about these, just treat them like any other file 15:25:59 sstewart6: ok, that makes life a lot easier 15:26:10 fisherii: i was thinking when we were talking about media we were talking about media streams 15:26:21 sstewart6: i don't think we're ready to tackle that one yet 15:28:22 Photo demo: http://shinydemos.com/photo-booth/ 15:29:46 Resolution: we'll support geolocation and screen orientation and handle media capture as standard file inputs; punt on everything else 15:30:30 Topic: Local storage and app cache and normal html caches 15:30:33 https://code.google.com/p/selenium/issues/detail?id=40 15:31:25 sstewart6: this is one of the oldest selenium bugs 15:31:28 fisherii: you can clear the cookies now 15:31:39 sstewart6: so that's interesting, since we can't clear the httponly cookies 15:31:56 sstewart6: so, clearing caches, can we do it, should we allow it 15:33:09 sstewart6: at google, people often wanted pre-warmed app caches so when they hit the site they could just start doing things 15:33:15 instead of going through all the hoops 15:33:26 fisherii: so they wanted to start with a known state 15:33:32 can't you do that in ff by serializing the profile 15:34:25 sstewart6: so there's three different caches, html and cookie cache, app cache, and local storage 15:34:40 plh: what about index db? 15:34:52 s/index/indexed/ 15:34:53 sstewart6: and indexeddb 15:35:22 fisherii: i assumes this is because the don't want to incur overhead of restarting the browser 15:35:34 sstewart6: or if they're using IE, which doesn't use a clean profile per run 15:35:51 sstewart6: or some mobile browsers 15:36:05 fisherii: I would find this useful personally, if we could nuke all of that state 15:38:11 plh: what about clearing security state or geolocation ...? 15:40:27 sstewart6: ok, so we don't support clearing caches midway thru, but we guarantee on start up things are in a clean state 15:41:40 fisherii: except IE can't guarantee clean state 15:41:44 sstewart6: the spec should aim high 15:42:07 John: you can tell IE to clean the state on exit 15:42:46 fisherii: ok, that's good; although there's still difficulty on mobile 15:43:48 sstewart6: should it be a should or a must 15:43:58 John: I think it should be a should 15:44:13 AutomatedTester: should be a must, but pragmatically a should 15:44:32 sstewart6: let's start with a must right now, and we'll have a chance for review 15:45:24 plh: is there a way to test this is implemented 15:45:35 sstewart6: yes, there is, load a file, delete it, and try to access it again 15:46:21 sstewart6: or we could stick a proxy in the way, start a new session, configure with a proxy, request a file, and then request it again, the first time with proper caching headers; restarting the browser, it should download the file again 15:46:40 plh: or you can just do local storage 15:46:44 fisherii: we want tests for all these aspects of state 15:46:53 fisherii: when we talk about the state, we should define what we mean 15:46:59 jhammel has joined #testing 15:47:03 jhammel has left #testing 15:47:11 sstewart6: i think you're right, anyone disagree? 15:48:02 Resolution: we're not going to support clearing caches midway through test, we will attempt to start browsers in a clean state, and we will define clean state, and we will write tests around these 15:48:08 plh: that's for clearing, what about setting 15:48:31 sstewart6: let's follow what we do for cookies now, you have to go to the domain 15:48:58 JohnJansen has joined #testing 15:49:20 sstewart6: it might be nice, but it's not a must 15:49:53 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/session_storage 15:50:04 fisherii: there is a spec in open source for local storage/session storage 15:50:25 sstewart6: i think just leave this in the open source spec, until there's a need for it 15:51:01 [lunch break] 15:51:01 RRSAgent, draft minutes 15:51:01 I have made the request to generate http://www.w3.org/2013/06/14-testing-minutes.html kkania 16:22:09 sstewart6 has joined #testing 16:23:00 kkania has joined #testing 16:30:58 scribe sstewart6 16:31:10 scribe:sstewart6 16:31:15 scribe: SimonStewart 16:31:23 scribe: gosh darn it, let me write 16:32:03 ScribeNick: sstewart6 16:32:08 RRSAgent, draft minutes 16:32:08 I have made the request to generate http://www.w3.org/2013/06/14-testing-minutes.html wilhelm 16:32:17 mdyck_ has joined #testing 16:32:20 Topic: naming of log nodes 16:33:07 How do we prevent collisions in log type names? 16:33:21 wilhelm: is it a real problem? 16:33:28 It's probably a problem on grid 16:33:42 https://dvcs.w3.org/hg/webdriver/raw-file/tip/webdriver-spec.html#logging 16:34:06 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/log/types 16:34:15 https://code.google.com/p/selenium/wiki/JsonWireProtocol#Log_Type 16:34:32 "server" is overloaded 16:35:52 Options: namespace log types, or allow intermediate nodes to rewrite type names 16:36:01 JohnJansen: Why not use namespaces? 16:36:05 plh: what would be wrong? 16:36:20 wilhelm: mentions xml namespaces in less than glowing terms 16:36:21 s/wrong?/wrong? :)/ 16:36:45 wilhelm: suggests namespacing by adding some unique key from the machine 16:38:36 wilhelm: so why not use unique keys based on the host? 16:38:57 Because the purpose of the logs is to provide consistent diagnostic data. Hard to do with string parsing 16:39:20 Perhaps add "name" and "host" to the log entry 16:39:32 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/log/types 16:40:07 https://code.google.com/p/selenium/wiki/JsonWireProtocol#/session/:sessionId/log 16:41:34 gdennis: Why do you need to find out the types of logs available to you? 16:41:47 Because you may not know which logs are available to you 16:41:55 gdennis: do the names contain meaning? 16:42:47 They can be arbitrary. 16:46:41 Conversation about what the purpose of the names are 16:48:18 gdennis: the "all" case needs to be handled, but could be done separately 16:51:01 JohnJansen: say I get back the strings and we've implemented this. I'd still do the "all" query if I wasn't sure which server was wanted 16:52:26 Conversation about highlighting different log types 16:52:35 (in a tool) 16:53:25 gdennis: you'd be okay if there was a distinctive log type called "all" since the type is in each entry 16:53:49 gdennis: not sure the "types" url is necessary 16:54:30 JohnJansen: as long as the log itself has a type, I'm not sure that the log types are necessary 16:55:16 Discussion about timestamps 16:56:29 http://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/logging/LogCombiner.html 16:56:52 kkania: you could have the browser and performance logs interleaved, provided everything was done on the same machine 16:57:20 gdennis: how do we prevent collision of log names 16:57:52 gdennis: add the ability to request a log name with a given prefix 16:57:59 JohnJansen: and that would be the namespace? 16:58:07 gdennis: possibly 16:58:38 kkania: but what about the case where there are two types of the same server on different machines? How would you distinguish? 16:59:17 JohnJansen: the log types don't have meaning, so you'd need to go through them and post-process 16:59:28 kkania: how would the client do the Right Thing for the user 16:59:42 gdennis: what's the format of a log type? 17:00:00 kkania: not defined. Normally just writing to some memory or a file 17:00:10 kkania: chromedriver tells chrome to log to a file 17:00:18 gdennis: what's the log type there? 17:00:22 kkania: browser 17:00:28 gdennis: where do you say that? 17:00:35 kkania: the client would request that 17:02:35 How do I request all "performance" logs? 17:03:55 Suggestion: three pieces of data needed to be sufficiently unique: name of log type, hostname/identifier, and server type 17:04:52 kkania: what about the case where there are two identical servers on the same host? 17:05:00 How about adding port to the hostname? 17:05:04