07:36:51 RRSAgent has joined #testing 07:36:52 logging to http://www.w3.org/2014/07/07-testing-irc 07:48:05 hmm 07:48:17 not sure we need RRSAgent logging this channel but ok 08:12:02 darobin has joined #testing 08:45:02 Ms2ger has joined #testing 08:53:47 ptressel has joined #testing 08:59:29 AutomatedTester has joined #testing 09:00:41 Automate_ has joined #testing 09:00:49 JohnJansen has joined #testing 09:00:57 simons has joined #testing 09:01:08 Greetings! 09:01:10 ShuotaoGao has joined #testing 09:01:12 MarcFisher has joined #testing 09:01:41 AutomatedTester has joined #testing 09:02:31 Morning y'all 09:02:57 lukeis has joined #testing 09:03:07 hola 09:03:10 jimevans has joined #testing 09:03:15 wow it's a simons 09:03:23 I LIVE! 09:03:45 simons: yeah I guess the rumors that you still exist are true 09:03:50 and I lost a best 09:03:53 *bet 09:03:55 Ha! 09:04:00 mdas has joined #testing 09:04:10 yay 09:04:17 It’s been an intense… 7 months or so 09:04:18 simons: I won't be at the f2f but I'm sure you guys will manage without me 09:04:18 hola! :) 09:04:36 simons: 7 months of vacation is certainly intense, yeah 09:04:39 I’m hoping that jgraham knows how the irc bot works 09:04:46 Vacation? Nope. Work 09:04:54 And “personal matters" 09:04:56 yeah just messing with you 09:05:06 Oh, right, I was going to review the spec this weekend 09:05:13 simons: I'll be around on IRC for the meeting if you need me 09:05:23 I have no idea 09:05:36 I know q+ and that's about it 09:06:19 JohnJansen has joined #testing 09:06:19 Ms2ger: you missed some fun, man. whatever other way you spent your weekend was a waste. but you still have time to get the fully enjoyment 09:07:47 Zakim has joined #testing 09:10:58 https://www.w3.org/wiki/WebDriver/2014-July-F2F 09:10:59 Ø 09:11:03 ø 09:11:08 that was surprisingly easy 09:11:09 æ 09:11:13 Arse 09:11:15 So close 09:11:32 Topic: Browser testing and tools WG F2F, London, July 7th 09:11:35 There's an ø key on my keyboard. See, easy. 09:11:39 Agenda: https://www.w3.org/wiki/WebDriver/2014-July-F2F 09:11:43 Chair: wilhelm 09:13:01 What's the special command we do to say we're present? 09:13:17 RRSAgent, draft minutes 09:13:17 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html wilhelm 09:13:40 oops wrong channel 09:14:29 Present+ ato 09:14:37 Present+ JohnJansen 09:14:38 Present+ ato 09:14:48 Present+ jimevans 09:14:49 Present+ ShuotaoGao 09:14:49 Present+ lukeis 09:15:01 Present+ Simon Stewart 09:15:04 Present+ Marc Fisher 09:15:09 Presnet+ Andreas Tolfsen 09:15:09 Present+ Malini Das 09:15:13 Present+ Andreas Tolfsen 09:15:24 Meeting: Browser testing & tools WG, F2F, July 7 09:15:26 present+ jgraham 09:15:27 Present+ Wilhelm 09:15:56 present+ David Burns 09:16:01 RRSAgent, make log public 09:16:21 RRSAgent, draft minutes 09:16:21 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 09:16:49 remi has joined #testing 09:17:13 Scribe: wilhelm 09:19:44 Present+ SimonStewart MarcFisher AndreasTolfsen MaliniDas DavidBurns 09:19:53 https://www.w3.org/wiki/WebDriver/2014-July-F2F 09:19:56 Ms2ger: heh thanks, I just noticed I'm both Malini and Das 09:20:02 Present- Simon Stewart Marc Fisher Andreas Tolfsen Malini Das David Burns ato 09:20:05 RRSAgent, draft minutes 09:20:05 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 09:20:06 Topic: State of the spec 09:20:36 RRSAgent, make minuts 09:20:36 I'm logging. I don't understand 'make minuts', MikeSmith. Try /msg RRSAgent help 09:20:38 RRSAgent, make minutes 09:20:38 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html MikeSmith 09:20:44 AutomatedTester: What has changed is: A lot of bugfixes. 09:21:04 ... There's been standardizing layout, so the document ahs a flow. 09:21:10 ... Adding JSON wire protocol endpoints. 09:21:14 Regrets+ MikeSmith 09:21:17 ... Filling in element state. 09:21:46 ... No major additions, mainly bugfixes. 09:22:00 ... If there's a bug for a missing section, that gets added. 09:22:32 RRSAgent, make minutes 09:22:32 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html MikeSmith 09:22:59 ... Properties and attributes. Should be split into distinct parts? 09:23:46 ato: WebIDL? We should discuss. 09:24:06 jgraham: The spec feels a bit confused and underdefined at the moment. 09:24:33 s/ahs/has/ 09:24:36 (Agenda point added for this.) 09:25:35 simons: Any issues with new sections? 09:25:40 JohnJansen: Touch stuff, but that's in the agenda. 09:26:18 ShuotaoGao: Security issue. 09:27:40 Topic: Which bits of the spec are missing? 09:28:00 simons: Current timeline says we should reach LC around September. 09:28:03 Lachy has joined #testing 09:28:05 wilhelm: (First last call.) 09:28:19 simons: We should figure out what we need to do to get to LC. 09:28:50 jgraham: *brings a stack of papers* 09:29:09 jgraham: I hadn't previously read the spec properly. I did so over the weekend. 09:29:20 ... Some structural issues. Some editorial, some more fundamental. 09:29:34 ... The history is a bit complicated. There's three things: 09:29:43 ... Client API. JSON protocol. Actual browser behaviour. 09:29:53 simons: Spec should define wire protocol, list of commands, expected behaviour. 09:29:58 simons: Client side is undefined. 09:30:02 jgraham: Sensible. 09:30:40 MarcFisher: Should we delete the WebIDL parts? 09:31:00 jgraham: WebIDL definitions for a theoretical client. 09:31:09 simons: SHould we define the JSON payloads instead? 09:31:30 jgraham: WebIDL is to be used for language bindings. JS bindings in particular. 09:31:37 jgraham: You want: "The command format is this..." 09:31:49 jgraham: "It takes an object that takes these keys..." 09:32:18 jgraham: Someone at some point must have written a JSON schema language. 09:32:34 simons: There's an JSON hyperschema. 09:32:44 http://json-schema.org/examples.html 09:32:56 MarcFisher: Aren't the tables we have sufficient? 09:33:13 RRSAgent, draft minutes 09:33:13 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 09:33:16 simons: We do the descriptions underneath. Nice to be able to glance at the spec and see which fields there are. 09:33:37 jgraham: It should define the message format. It should be like a switch table. 09:34:09 jgraham: Once you have an object on the browser side, you need to explain how to get a value out of it. 09:34:19 simons: Parameters tell you what parameters there are. 09:34:31 gitbot has joined #testing 09:34:31 [13web-platform-tests] 15dontcallmedom closed pull request #1092: Tagging all instructions to human testers. (06master...06master) 02https://github.com/w3c/web-platform-tests/pull/1092 09:34:31 gitbot has left #testing 09:34:32 gitbot has joined #testing 09:34:32 [13web-platform-tests] 15dontcallmedom pushed 2 new commits to 06master: 02https://github.com/w3c/web-platform-tests/compare/8f89a2f16189...5c7d6394a1e8 09:34:32 13web-platform-tests/06master 145d70831 15Patrik Höglund: Tagging all instructions to human testers. 09:34:32 13web-platform-tests/06master 145c7d639 15Dominique Hazael-Massieux: Merge pull request #1092 from phoglund/master... 09:34:32 gitbot has left #testing 09:34:54 jgraham: If someone sends you a message with a missing command, what happens then? 09:34:58 jgraham: This should all be defined. 09:35:09 jgraham: There should be an algorithm in the spec defining all this. 09:35:42 simons: If we change WebIDL to JSON, and maybe beef up section 2, that would address the things you're talking about? 09:35:50 jgraham: First part. Getting as far as getting data in the commands. 09:36:19 jgraham: SHould have a list of steps. 09:36:24 jgraham: "If it's missing..." 09:36:41 jgraham: If you send a get message and there is no URL in that, what should happen? 09:37:13 jgraham: Say you've got the URL, it should have steps. From the current spec prose, should it be a relative URL or an absolute URL? 09:37:18 jgraham: What should happen if there is an error? 09:37:39 jgraham: The current spec describes a selection of cases, but not all. 09:37:41 s/SHould/Should/ 09:37:56 jgraham: It should call into the HTML navigate algorithm... 09:38:27 jgraham: "Cause the browser to navigate to a new location" is vague. 09:39:10 MarcFisher: We want the behaviour the browser to match the actual browser. 09:39:44 HTML5 navigation algorithm: http://dev.w3.org/html5/spec-LC/history.html#browsing-the-web 09:39:48 MarcFisher: Failing to follow the HTML navigate algorithm shouldn't block compliance with _WebDriver_. 09:40:30 jgraham: "Navigate" is not a defined term here. 09:40:40 WebDriver should behave the same as the (possibly buggy) implementation of the HTML algorithm 09:41:08 simons: Could you be compliant with the WebDriver spec with a buggy HTML navigation implementation? 09:41:16 jgraham: It's a bit of a moot point. 09:41:27 jgraham: We should't be vague instead. 09:41:37 simons: If we use should instead of must... 09:41:42 jgraham: Weasel-wording. 09:41:58 There's no reason to not require it 09:42:41 MarcFisher: If the spec requires this algorithm, we should test it... 09:42:56 jgraham: In reality, that sort of conformance testing doesn't happen. 09:43:03 jgraham: The right answer is not to be vague. 09:43:05 simons: I agree. 09:43:11 simons: How do we do that in a way that allows...? 09:43:31 simons: Things like get are used by native mobile to get UI elements. 09:43:54 AutomatedTester: We could have different codepaths. If you're native, then do this... 09:44:06 MarcFisher: Android vs iOS? 09:44:30 MarcFisher: If they're treated as opaque strings, should we uniformly do this? 09:44:34 simons: That's the other extreme. 09:45:27 jgraham: If you want to know when the page load is finished, HTML defines this. 09:45:40 jgraham: Two of the spec's loading strategies are equivalent. 09:45:59 simons asks wilhelm for input: 09:46:12 wilhem: Now all we need to do is make it more like a real spec 09:46:46 wilhelm: which means we’ve solved most of the technical questions (other than the bug list), but we should think about taking in all of jgraham’s input and have the spec match that. 09:47:53 ACTION: jgraham to submit patch for get 09:48:06 ACTION: jgraham to submit bugs for the other issues 09:49:06 (Tangent on naming of get.) 09:50:09 jimevans1 has joined #testing 09:50:23 simons: Is the purpose of the spec to tidy up all the rough edges from...? 09:50:24 MarcFisher: Yes. 09:50:34 MarcFisher: Spec already breaks compat with existing clients. 09:50:48 MarcFisher: Let's do it right. 09:52:24 simons: Should we clean up the method names? 09:52:39 mdas: We should define window and frame. 09:52:48 mdas: (Swtich to frame, switch to window.) 09:53:24 https://www.w3.org/Bugs/Public/show_bug.cgi?id=23020 09:54:49 jgraham: Should URLs be absolute or relative? 09:54:52 simons: Absolute. 09:54:54 jgraham: This is undefined. 09:55:13 AutomatedTester: Each implementation returns a different scary error message. 09:55:52 jgraham: There's probably an algorithm for determining if something is an absolute URL. 09:56:17 simons: Do anyone object to cleaning up the command names? 09:56:47 JohnJansen: With implementations on the books with the current methods, this seems like work... 09:57:05 MarcFisher: The only one that jumps out to me at the moment is get. 09:57:29 AutomatedTester: Same cleanup is needed for the open source project. 09:58:24 lukeis: There are a few breaking changes... 09:58:34 jimevans1: Error codes. 09:58:53 ato: There are some other commands that are conflicting and misleading. 09:58:57 ato: clear is another example. 09:59:04 RRSAgent, draft minutes 09:59:04 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 09:59:07 ato: All methods under alerts. 09:59:25 ato: I don't think they have the correct names. sendKeys. 09:59:33 ato: getText 09:59:35 Methods that I’m aware that people want to change: “get”, “clear”, “alerts commands” 10:01:28 “submit” too 10:04:31 (Discussion on whether or not to include the submit command.) 10:05:49 lukeis1 has joined #testing 10:08:55 ACTION: MarcFisher to not document submit 10:11:11 ACTION: AutomatedTester to retrofit seciton 17 through all commands 10:11:38 lukeis has joined #testing 10:12:50 get 10:12:50 clear 10:12:50 alert 10:12:50 dismiss 10:12:50 accept 10:12:50 sendKeys 10:12:50 getText 10:13:27 https://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html#widl-Alerts-dismiss-void 10:14:30 ato: Screenshots are not complete. 10:15:24 AutomatedTester: We discussed scrolling or not scrolling in our last meeting. Mainly around reftests and position:fixed; 10:16:30 I’ve updated the spec and removed the reference to “submit" 10:17:15 ACTION: JohnJansen to describe what he wants for screenshots (scrolling vs not scrolling) 10:19:29 ACTION: simons to move "scaling the content of windows" to level 2 10:21:56 AutomatedTester: Section 10 is missing "enabled" and "isInteractable". 10:23:59 jgraham: The platform uses "clicking" for a lot of things... 10:24:44 AutomatedTester: Use case: CSS transforms. 10:25:59 simons: We want to support multiple implementations of user interactions. Absolute position at the screen. Relative to top left of the DOM. In the current equivalent of hwind. ... 10:26:30 simons: There are implementations that do advanced user interactions on the local end. 10:26:38 simons: Drag something from the desktop into the browser. 10:26:54 AutomatedTester: You can do that with JS. get bounding client rect. 10:28:04 https://www.w3.org/Bugs/Public/show_bug.cgi?id=24995 10:29:38 simons: To allow dragging from elements into the browser: location in the DOM, location on the monitor (not included in the spec), location in the equivalent to hwind. 10:29:52 simons: If you're on OSX, this doesn't exist. 10:29:59 Example possible text for "get" https://pastebin.mozilla.org/5528630 10:30:15 JohnJansen: Out of scope? 10:30:21 AutomatedTester: Outside of the window is out of scope. 10:30:43 JohnJansen: Not for this spec. 10:31:15 simons: Use case: Drop photos into the browser. 10:31:31 AutomatedTester: That's in the operating system.. 10:31:32 simons: Yes. 10:32:08 (simons illustrates on whiteboard. Beautiful art.) 10:39:14 RRSAgent, draft minutes 10:39:14 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 10:44:09 (Continued discussion of whether or not to return the absolute position of an element on the screen. Source code being discussed.) 10:44:21 MarcFisher: Should this be in level 1? 10:44:25 simons: I can't see why not. 10:44:55 AutomatedTester: I'd lean towards not having it. 10:45:01 JohnJansen: Agreed. 10:46:08 simons: Should we have one command merging size and location? 10:46:13 MarcFisher: I'm fine with that. 10:46:22 ato: Size is already exposed via JS. 10:46:40 MarcFisher: Many things are accessible via JS, but we expose them via the wire protocol. 10:46:54 MarcFisher: (Native testing.) 10:48:12 simons: location(x,y) should be relative to 0,0 of the DOM? 10:48:27 RESOLUTION: location(x,y) should be relative to 0,0 of the DOM 10:48:54 simons: location equivalent to getClientBoundingRect? 10:48:59 (No votes for that.) 10:49:20 simons: location equivalent to current operating system window handle? 10:49:30 (No votes for that.) 10:49:46 simons: location relative to the physical display? 10:49:52 (No votes for that.) 10:51:20 abarsto has joined #testing 10:52:30 simons: Should we discuss merging size and location? 10:52:40 JohnJansen: I don't see why we want to do that. 10:52:58 simons: Use case: Sauce labs on a different continent. Saves a roundtrip. 10:53:27 AutomatedTester: It already gets all the data for getClientBoundingRect. 10:54:00 http://www.w3.org/TR/2014/WD-geometry-1-20140522/#DOMRect 10:54:13 MarcFisher: What would we call this merged thing? 10:54:20 getElementRect? 10:54:22 http://dev.w3.org/fxtf/geometry/#DOMRect 10:54:31 ato: (Refers to DOMRect) 10:54:49 Given that there's discussion about having multiple drafts, who's volunteering to do the additional busywork? 10:55:56 AutomatedTester: How about CSS shapes? You could return the actual shape... 10:56:20 AutomatedTester: Return an object? 10:56:55 ato: What properties? 10:57:03 simons: size and location 10:57:22 simons: We can define this in terms of DOMRect. 10:57:42 simons: Do we want an additional command? 10:57:46 MarcFisher: Replace. 10:57:53 AutomatedTester: More a merge than a replace... 10:58:18 MarcFisher: Language bindings could just alias these. 10:58:34 simons: Quick vote on merging element location and element size? 10:58:46 JohnJansen: Why not call getBoundingClientRect? 10:59:02 AutomatedTester: It's relative to viewport. 10:59:12 JohnJansen: Argument is: two roundtrips vs one. 10:59:19 simons: Yes. 11:00:33 ACTION: AutomatedTester to merge element location and size into getElementRect 11:14:09 Zakim has left #testing 11:51:41 MarcFisher has joined #testing 11:52:07 ShuotaoGao has joined #testing 11:53:03 remi has joined #testing 12:02:25 http://www.themeatmarket.co.uk/ 12:05:45 Actions from last time: 12:05:46 http://www.w3.org/2014/02/26-testing-minutes.html 12:05:50 http://www.w3.org/2014/02/25-testing-minutes.html 12:07:11 http://38.media.tumblr.com/21801c47ccff06fa5e6612aea5b87095/tumblr_mlqdctiGeH1rvsbh9o1_500.jpg 12:07:12 Scribe: MarcFisher 12:10:32 https://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html#reporting-errors 12:11:49 mdas: Section 11.4 JavaScript error reporting is empty. 12:12:18 simons: return javascript error object and optionally stack trace in the response. 12:14:04 http://31.media.tumblr.com/82ad44a2be111c6732e9ebff2a046daf/tumblr_n7ab3elDle1rvsbh9o1_500.png 12:15:04 Action: AutomatedTester will update Section 11.4 with simons proposal 12:16:52 simons: not adding onError support, but can shove js errors to logs. 12:19:25 AutomatedTester: do we need to add delete cookie support. 12:19:43 simons: sounds like delete cookie would not be fun to implement. 12:20:28 AtuomatedTester: spec currently suggests deleting cookie by setting expiry to the past. 12:21:31 plh has joined #testing 12:22:38 s/AtuomatedTester/AutomatedTester/ 12:22:56 Ms2ger: <3 12:23:33 ShuotaoGao: can we delete httpOnly cookies with this work around. 12:24:12 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25008 12:24:14 simons: probably not, but with the way cookies are usually used, this probably doesn't matter. 12:24:23 RRSAgent, draft minutes 12:24:23 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 12:24:31 Let's resolve the bug so we don't discuss again when going through bugs 12:25:06 Action: AutomateTester document how to delete httpOnly cookies 12:25:19 s/AutomateTester/AutomatedTester/ 12:29:28 Add support for getting timeout values. 12:30:20 simons: get the all as one go? 12:30:27 many people: probably 12:31:34 AutomatedTester: rename timeouts to setTimeouts in level 1. getTimeouts can be in level 1 or level 2. 12:32:30 MarcFisher: pass in a map of timeouts in renamed setTimeouts 12:34:36 jimevans1: page load timeout of -1, never timeouts. 12:36:10 Action: add how timeouts should be handled in Section 5.1.1 12:37:17 jgraham: should have a wait for page load algorithm that is referred to from get (and anywhere else) 12:37:24 https://www.w3.org/Bugs/Public/show_bug.cgi?id=26275 12:37:25 https://www.w3.org/Bugs/Public/show_bug.cgi?id=26275 12:39:05 Action: review jgraham's draft for get (in https://www.w3.org/Bugs/Public/show_bug.cgi?id=26275) for handling of timeouts and page loading strategy 12:40:12 Action: rename timeouts to setTimeouts and change to take dictionary 12:47:31 Resolution: don't add getTimeouts to level 1, save for level 2. 12:48:24 I don't think RRSAgent recognizes Resolution:? 12:48:49 Or maybe it's just for the minutes. 12:55:45 MarcFisher: section 15.2 looks incomplete 12:56:09 MarcFisher: do we even need it? 12:56:12 simons: yes 12:56:44 discussion about what should be done with Section 15.2 12:57:29 Action: simons define how to handle modal windows 13:01:24 RESOLVED: don't add getTimeouts to level 1, wait for level 2. 13:02:52 AutomatedTester: is the takesScreenshot capability useful. 13:03:10 RESOLVED: keep screenshot capabilities 13:13:43 MarcFisher: I don't like the note in Section 18.1 as the table it references doesn't reflect the current browser ecosystem. 13:13:56 simons: I will remove the note. 13:14:54 Action: simons will create something to generate Appendix A 13:15:53 gitbot has joined #testing 13:15:53 [13web-platform-tests] 15dontcallmedom closed pull request #277: peerconnection api tests (06master...06submission/robo) 02https://github.com/w3c/web-platform-tests/pull/277 13:15:53 gitbot has left #testing 13:16:04 Action: simons will create something to generate Section C 13:16:54 simons: work on strawman for Section E logging 13:26:46 simons: drew straw man proposal on whiteboard 13:27:29 jimevans has joined #testing 13:27:53 simons: do we want to support paging of logs in level 1? 13:28:03 https://lh3.googleusercontent.com/-TyFnpMYf7Lo/U7qgSN9PqmI/AAAAAAAAFOo/qaKthN50320/w764-h573-no/IMG_20140707_142707.jpg 13:28:31 lukeis: if a log is fetched, is it purged? 13:28:46 simons: I think so 13:29:04 AutomatedTester: have an argument for deleting 13:29:13 simons: have a command to get log names and host names 13:29:34 remi has joined #testing 13:29:40 simons: have another command to get logs with an optional host name, log name, and purge boolean 13:31:02 AutomatedTester: how do we handle cases where links in the chain are broken? 13:31:11 simons: we go as far up the chain as we can 13:31:54 JohnJansen: how do we prevent hostname clashes and logname clashes? 13:32:07 simons: I am not sure how we prevent this. 13:32:25 jgraham: why do we want to use a hostname anyways? 13:32:37 simons: okay, maybe not a hostname, but some sort of a key 13:33:05 ShuotaoGao: use a role key 13:34:08 simons: combination of role key and hostname, and if you have a clash that is a terrible pity 13:35:08 MarcFisher: do we like the straw man? 13:36:28 ato: alternative would be listener on the logs for different nodes. 13:37:08 seva has joined #testing 13:37:10 jimevans: one controversy is what types of logs. Are we prescribing log types? 13:37:24 simons: I won't prescribe logs at this time. 13:37:37 Vsevolod Lotoshnikov came in. 13:38:31 Ms2ger: ^ how do we add Seva with Present ? 13:39:40 mdas: Logging doesn't make sense in this spec? 13:40:30 simons: you should implement logging, and if you do, you must conform to this spec. 13:41:02 jgraham: makes just as much sense to say that you must implement this, but return empty. 13:42:10 RESOLVED: push logging to level 2. 13:42:53 Action: simons delete section E logging 13:43:17 MarcFisher: does RESOLVED work? I thought it was Resolution? 13:44:08 MarcFisher: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm?content-type=text/html#Quick_Start_Guide seems to point to RESOLUTION 13:45:08 mdas: yeah, looks like you are right 13:45:27 RESOLUTION: push logging to level 2 13:45:36 https://www.rfc-editor.org/rfc/rfc3514.txt 13:46:11 Present+ VsevolodLotoshnikov 13:46:23 RRSAgent, draft minutes 13:46:23 I have made the request to generate http://www.w3.org/2014/07/07-testing-minutes.html Ms2ger 13:47:42 Discussion of Section F, security and privacy. 13:47:47 MarcFisher: I don't think I can set resolutions, so there are 2 other instances of Resolved that needs to be recorded: "RESOLVED: keep screenshot capabilities" and " RESOLVED: don't add getTimeouts to level 1, wait for level 2." 13:48:09 RESOLUTION: keep screenshot capabilities 13:48:20 RESOLUTION: don't add getTimeouts to level 1, wait for level 2. 13:48:41