00:17:51 RRSAgent has joined #testing 00:17:51 logging to https://www.w3.org/2019/09/16-testing-irc 00:18:45 Agenda: https://docs.google.com/document/d/1_d2xUBgNn6nmiIXM6m9zSLjzYhvDS4LMrmgoxMQJKuU/edit# 00:19:09 RRSAgent: Make logs public 00:19:13 Is it "present+ "? 00:19:42 Komehyo 00:19:46 Uh, https://www.w3.org/2002/03/RRSAgent 00:20:01 Present+ 00:20:12 Present+ 00:22:42 RRSAgent: make minutes 00:22:42 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html jgraham 00:27:08 https://blog.mozilla.org/opendesign/firefox-the-evolution-of-a-brand/ 00:27:12 estes has joined #testing 00:27:31 (14wpt) [PR] moz-wptsync-bot requested 13#19070 merge into 07master: [Gecko Bug 1315892] text-orientation: upright' forces used 'direction' to LTR. - https://git.io/JeOvA 00:31:17 Hexcles has joined #testing 00:31:46 present+ 00:31:57 present+ 00:31:57 present+ 00:31:59 present+ 00:32:00 present+ 00:32:04 present+ 00:32:06 zcorpan has joined #testing 00:32:10 present+ 00:32:19 present+ 00:32:19 jgraham: that's how you do it. 00:32:24 https://bocoup.com/blog/how-to-scribe-at-tpac 00:32:34 present+ 00:32:44 zghadyali_ has joined #testing 00:33:16 present+ 00:33:20 present+ Simon Pieters, Bocoup 00:33:22 Zakim has joined #testing 00:33:25 dxie_ has joined #testing 00:33:26 present+ David Burns, Mozilla 00:33:39 RRSAgent: halp! 00:33:39 I'm logging. I don't understand 'halp!', Hexcles. Try /msg RRSAgent help 00:33:39 present+ Philip Jägenstedt, Google 00:33:44 present+ Andreas Tolfsen (Mozilla) 00:33:47 present+, Daniel Xie, Google 00:34:07 present+ Robert Ma (Google) 00:34:09 present+ Zoher Ghadyali, Microsoft 00:34:25 scribenick: foolip 00:34:44 lukebjerring: we have an Agenda in a doc, will work on that after first break 00:34:50 present+ John Chen, Google 00:34:52 present+, Qiuyi(Joyee) Zhang, Igalia 00:34:57 lukebjerring: first status updates: https://docs.google.com/presentation/d/10pP5UdurCE3_5YMk6ds8ksz5GIj_Bxixfi9GJP2LOkw/edit?usp=sharing 00:35:28 yigu has joined #testing 00:37:32 lukebjerring: the dents in the Safari graph are infrastructure issues that affected reults 00:37:46 present+ 00:38:41 RRSAgent, make minutes 00:38:41 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 00:38:48 agenda? 00:39:18 jgraham: big change for Firefox is rewrite of encodings 00:39:41 RRSAgent: make minutes 00:39:41 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html ato 00:40:51 lukebjerring: browser-specific failures and passes are interesting for interoperability 00:40:58 Present- Bocoup 00:41:06 Present- Mozilla 00:41:18 Present- Google 00:41:33 Present- Andreas 00:41:39 Present- Tolfsen 00:41:40 yigu has joined #testing 00:41:47 Present- (Mozilla) 00:41:54 Present- (Google) 00:42:01 Present- Microsoft 00:42:09 Present- Igalia 00:42:24 RRSAgent, make minutes 00:42:24 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 00:42:52 jugglinmike1: yes! 00:43:06 jugglinmike1: meet.google.com/xyo-wzse-nss 00:43:15 Orphis has joined #testing 00:43:22 jugglinmike1: I thought you'd be out for the day 00:43:45 present+ gsnedders 00:43:57 example of is:different: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=is%3Adifferent 00:44:03 kevers has joined #testing 00:44:09 Present+ 00:44:17 jugglinmike1, I can webrtc you in 00:44:22 example of the `all` query: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=all%28status%3Aerror%29 00:44:54 present+ Yi Gu, Google 00:45:05 jugglinmike1: can you join? I'll have to click OK 00:45:21 jugglinmike1: good? 00:45:40 s/jugglinmike1:/jugglinmike1,/ 00:45:46 RRSAgent, make minutes 00:45:46 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 00:46:29 present 00:46:55 Hexcles: I'll do a live demo now! 00:47:04 Orphis has joined #testing 00:47:30 present+ Yi_Gu 00:47:38 Present- Google 00:47:42 RRSAgent, make minutes 00:47:42 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 00:48:19 Present- Ma 00:48:24 present+ Kevin Ellis 00:48:39 present- Robert 00:48:49 Title: Web Platform Tests, Day 1, TPAC 2019 00:48:57 present+ Robert_Ma 00:49:09 present- Kevin_Ellis 00:49:15 present+ Kevin_Ellis 00:49:21 present- Kevin 00:49:28 present- Ellis 00:50:23 s/jugglinmike1: can you join? I'll have to click OK/ 00:50:32 s/jugglinmike1, good?/ 00:50:50 RRSAgent, make minutes 00:50:50 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 00:53:01 i/we have an Agenda/Topic: Intro from Luke Bjerring 00:53:19 Meeting: Web Platform Tests, Day 1, TPAC 2019 00:53:27 RRSAgent: make minutes 00:53:27 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html ato 00:53:45 i/live demo/Topic: Live demo from Robert Ma 00:53:48 RRSAgent, make minutes 00:53:48 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 00:55:17 RRSAgent: agenda? 00:55:17 I'm logging. Sorry, nothing found for 'agenda' 00:57:52 jgraham: Taskcluster is going to split into separate instances for Gecko CI and rest of world, will give us new URLs and new UI 00:58:08 jgraham: hope to do Android x86 emulator on Taskcluster by end of year 00:59:00 jgraham: want to run Chrome and Firefox. much more capacity limits than desktop 00:59:07 jgraham: will probably start with daily runs 00:59:35 foolip: also trying to get WebKitGTK running 01:00:20 jgraham: trying to add decision task for Taskcluster, would allow us to schedule dependent tasks 01:00:33 jgraham: for example, we can avoid getting different versions of Firefox 01:00:49 jgraham: or could have a build job 01:02:21 JohnJansen: Edge is now a Chromium browser 01:02:43 JohnJansen: have looked to take advantage of wpt.fyi. 99.9% results are the same a Chrome, so differences are interesting 01:03:04 JohnJansen: we have found bugs (regressions) where Edge is different to Chrome 01:03:18 JohnJansen: we aim to be 24 hours behind Chrome 01:03:32 JohnJansen: but we also have different features that can cause tests to break. usually turns into blocking bugs 01:03:39 JohnJansen: really appreciate the interop view 01:04:01 JohnJansen: when will Edge stable be released? we're bug driven, not date driven 01:04:18 JohnJansen: beta felt very stable to me, very impressed by quality of Chromium out of the box. 01:04:45 karl has joined #testing 01:04:59 JohnJansen: wpt.fyi has helped us immensely. interesting to see the pass rate increase so much, now differences are really important 01:05:20 wanming has joined #testing 01:05:34 https://wpt.fyi/results/?label=master&label=experimental&product=chrome&product=edge&aligned&q=is%3Adifferent is a view that might be helpful 01:06:04 foolip: I can talk docs 01:07:11 agenda: https://docs.google.com/document/d/1_d2xUBgNn6nmiIXM6m9zSLjzYhvDS4LMrmgoxMQJKuU/edit# 01:08:10 https://wpt.fyi/interop/IndexedDB/idbobjectstore_createIndex15-autoincrement.htm?label=master&label=experimental&product=chrome&product=edge&aligned&diff&filter=ADC 01:08:21 jugglinmike1: we've been working to improve the docs over the past year 01:09:33 Orphis has joined #testing 01:10:06 jugglinmike1: we've switched for GitHub pages (Jekyll) to Sphinx, a Python project 01:11:02 See Mike's screen for the figure here: https://meet.google.com/xyo-wzse-nss 01:11:50 example search result https://web-platform-tests.org/search.html?q=assert_throws&check_keywords=yes&area=default 01:12:21 jgraham: thanks for improving the docs, it's a big improvement compared to what we had 01:12:27 Docs: "2019 WPT Documentation Improvements" https://docs.google.com/document/d/16KJbWVRtIjZQX80CQhOvwG2RHlIqVM1ADQTG1Q-QdlE/edit 01:12:34 RRSAgent, make minutes 01:12:34 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 01:13:05 jgraham: Another update. We've now moved from Travis to GitHub Actions. Somewhat mixed results, some spurious failures. Mostly things that require a github token, because the secrets handling is easier 01:13:40 plh has joined #testing 01:13:58 JohnJansen: some differences we see between Chrome and Edge might be because we run on Windows too. 01:14:18 lukebjerring: let's break for food 01:14:30 jgraham: let's be back here at 10:45 01:14:47 (i.e. in 30min) 01:15:05 Hexcles has joined #testing 01:17:56 denis has joined #testing 01:22:23 plh_ has joined #testing 01:23:06 flackr has joined #testing 01:24:00 present+ 01:24:12 present+ 01:24:22 present+ Mike Taylor 01:24:55 RRSAgent, make minutes 01:24:55 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html miketaylr 01:25:20 present- Mike 01:25:22 present- Taylor 01:25:24 present+ 01:25:26 RRSAgent, make minutes 01:25:26 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html miketaylr 01:29:33 Orphis has joined #testing 01:30:49 plh has joined #testing 01:33:54 tidoust has joined #testing 01:34:11 Orphis has joined #testing 01:36:23 Orphis has joined #testing 01:39:32 karl has joined #testing 01:43:22 estes has joined #testing 01:44:38 Orphis has joined #testing 01:46:10 Hexcles has joined #testing 01:47:26 kevers has joined #testing 01:51:21 Meeting: Web-Platform-Tests TPAC 2019 01:51:36 RRSAgent, make minutes 01:51:36 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html JohnJansen 01:55:47 zghadyali has joined #testing 01:56:00 JohnChen has joined #testing 01:57:32 zcorpan has joined #testing 01:58:26 back. intros... 02:01:42 JohnJansen: if you add `(edge:!pass&edge:!ok)` to the diff query you can see the stuff that's more likely a problem 02:02:37 karlcow_ has joined #testing 02:03:42 jorydotcom has joined #testing 02:03:52 +present Jory Burson, Bocoup 02:04:04 spectranaut has joined #testing 02:04:08 @jugglinmike1 sleep tight :D 02:04:20 lol 02:04:25 present+ Valerie Young, Bocoup 02:04:47 present+ Jory Burson, Bocoup 02:05:59 marcosc has joined #testing 02:06:54 so who have we agreed CSS WG joint meeting with on the CSS WG side? 02:13:05 RRSAgent, make minutes 02:13:05 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 02:13:50 present- Bocoup 02:14:03 RRSAgent, make minutes 02:14:03 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 02:14:29 We're now doing Agenda smithing 02:15:20 (14wpt) [PR] chromium-wpt-export-bot requested 13#19071 merge into 07master: Port two webkit-xxx-interpolation.html to wpt/ - https://git.io/JeOJr 02:15:53 (14wpt) [PR] chromium-wpt-export-bot requested 13#19072 merge into 07master: Delete three webkit-xxx-interpolation.html - https://git.io/JeOJK 02:16:00 jugglinmike has joined #testing 02:17:03 because https://wiki.csswg.org/planning/tpac-2019#tuesday doesn't have any joint meeting with us there? 02:21:58 plh_ has joined #testing 02:23:46 JayZhou has joined #testing 02:31:44 yigu_ has joined #testing 02:34:41 xiaoqian has joined #testing 02:36:22 https://www.w3.org/wiki/TPAC/2019/SessionIdeas 02:36:34 https://w3c.github.io/tpac-breakouts/sessions.html 02:39:38 scribenick: foolip 02:39:43 Review of 2019 priorities from last TPAC starting 02:39:57 https://docs.google.com/document/d/1UE2KB7gvaEw5gvp4aAQNS9TrFYmnzgDzh5Sr4LQqaQo/edit?usp=sharing 02:40:38 TOPIC: Review of 2019 priorities from last TPAC starting 02:40:44 scribenick: zcorpan 02:42:48 zcorpan: documentation has been worked on 02:42:56 lukebjerring: i like the improved docs! 02:43:14 AutomatedTester: improve debugging, this has to do with reftests 02:43:24 AutomatedTester: improving tooling about getting debugging info out 02:43:31 jgraham: duplicate with the later bullet point 02:44:06 JohnJansen: last year i couldn't figure out how to debug a test in python 02:45:25 ato: multiprocess debugging in python is fundamental limitation 02:45:37 JohnJansen: nobody knows how to debug a test running through wptrunner? 02:45:43 jgraham: in wdspec test? 02:45:45 spectranaut has joined #testing 02:45:46 JohnJansen: yes 02:45:51 jgraham: i don' tknow how to do that 02:46:01 foolip: printf() 02:46:17 jgraham: dunno if something spins up a new python process 02:46:19 gsnedders: yes 02:46:40 jgraham: maybe pause before the process starts and get the process id 02:46:44 RRSAgent, make minutes 02:46:44 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html MikeSmith 02:47:09 JohnJansen: reftests have clearly improved in wpt.fyi 02:47:29 ato: pytest subprocess 02:47:40 ato: command line flag to something something 02:48:12 jgraham: the wdspec case is really one process, other things is waiting on it 02:48:26 jgraham: if waiting time is indefinite, which i think we can, then it could work 02:48:46 ato: also webdriver related timeouts you need to tweak 02:48:56 jgraham: for other test types we try to do that 02:49:11 jgraham: disabling timeouts when running gdb debugger 02:49:32 ato: we've set timeout multiplier to something very high 02:49:43 lukebjerring: feature request? 02:49:48 JohnJansen: i'm logging one 02:50:04 RRSAgent, make minutes 02:50:04 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html JohnJansen 02:50:07 foolip: async_cleanup is major thing that happened 02:50:29 foolip: how many have used reftests? 02:50:33 (show of hands) 02:51:42 (14wpt) [issue] thejohnjansen opened 13#19073: We need a way to attach a debugger to the executing test when run from wptrunner - https://git.io/JeOUk 02:51:58 gsnedders: "has the assignee reviewed" is a metric we can check 02:52:01 I logged an issue for debugging tests: https://github.com/web-platform-tests/wpt/issues/19073 02:52:14 foolip: i set a filter to prio PRs where i'm assigned 02:52:32 https://github-health.appspot.com/ 02:52:49 lukebjerring: for people who use github-health this helps 02:53:15 jgraham: interesting to see if it's working for ppl who are not on infrastructure 02:53:37 What Mozilla uses: https://addons.mozilla.org/en-US/firefox/addon/myqonly/ 02:53:52 foolip: i look at things i'm assigned to 02:53:58 zcorpan: me too, or reassign 02:54:01 Shows a notification in your browser for GitHub items you are assigned to. 02:54:08 foolip: ideas for wpt-pr-bot? 02:54:21 jgraham: improved a bit, but hasn't shifted a lot 02:55:02 gsnedders: how many of the 250 PRs from 2017 are still open? 02:55:41 gsnedders: we need people who work on this 02:55:46 gsnedders: we've tried for years 02:56:54 foolip: teaching people how to do email filtering works 02:57:35 zcorpan: we know that new contributors don't have a good time 02:57:42 scribenick: foolip 02:57:42 zcorpan: their PRs are stuck for years 02:57:55 zcorpan: do we want their contributions from people who don't already work on browser engines? 02:58:20 zcorpan: if the answer is no we shouldn't pretend that we accept PRs, but if we do we should allocate time to do the review 02:59:09 s/work on this/work on the web features in question to review them/ 02:59:20 jgraham: the problem is who are the we who should do the reviews? 02:59:43 jgraham: ownership is fine-grained and we don't have a way to enforce that people do their job 03:00:12 zcorpan: we can explore incentives to do reviews, like celebrate those who do the most reviews 03:00:22 +1 03:02:40 tidoust has joined #testing 03:04:17 jgraham: it might be not worthwhile in the moment, but in the long run it may be 03:04:42 jgraham: choice between possible impact over a long period vs definite impact over short period 03:05:02 ato: are we sure that a stale review has been considered 03:05:12 ato: if nobody has looked at it, how do we know if it's important 03:05:24 miketaylr: has anyone retriaged? 03:05:39 miketaylr: might be 50 out of the 440 that are amazing 03:05:59 jgraham: i think we classify things in terms of their status (waiting for review, waiting for OP) 03:06:14 jgraham: don't classify by importance, size 03:06:47 miketaylr: if i say to other person at moz that 50 tests are important, it can be prioritized 03:06:58 jgraham: if we can sort things by stuff that show browser issues 03:07:08 jgraham: that is valuable 03:07:14 foolip: come back to this? 03:07:17 jgraham: yes 03:07:24 tidoust has joined #testing 03:08:03 jgraham: next bullet point: beginners onboarding 03:08:14 foolip: more to say that docs? 03:08:38 jgraham: mdn survey 03:09:08 foolip: i think that survey can be helpful to prioritize our work 03:09:27 jgraham: "make CI more robust" 03:09:30 foolip: i think we did 03:09:48 foolip: reliability question, can talk about PRs in next session 03:09:59 foolip: running more, getting more complete results 03:10:04 jgraham: problems with safari 03:10:05 (14wpt) [PR] chromium-wpt-export-bot 04closed 13#18999: Revert "Reland "Started implementing the STAPIT algorithm"" - https://git.io/Jemrw 03:10:27 foolip: github actoins acting up, problems for PRs 03:10:45 foolip: PR results and full run are better now than 1 year ago 03:10:58 jgraham: "give web platform engineers the tools they need to prio" 03:11:21 jgraham: is done or in progress 03:11:28 gsnedders: don't have bug links 03:11:32 jgraham: so that's in progress 03:12:17 lukebjerring: every bug that i triage that has a crbug is fixed or explanation why it won't be in the short term 03:12:28 lukebjerring: made some progress there 03:12:54 foolip: would you encourage others to do the same? 03:12:56 lukebjerring: yes 03:13:13 lukebjerring: https://wpt.fyi/insights 03:13:23 lukebjerring: double down on what is an important failure, not yet really solved 03:13:37 lukebjerring: RFC https://github.com/web-platform-tests/rfcs/pull/16 will move the needle more significantly 03:13:50 jgraham: we've looked at firefox-only failures 03:14:08 jgraham: triage that but resistance is always "ok these things fail but are they relevant to compat?" 03:14:21 jgraham: we know if we fix compat bugs they often end up with new tests 03:14:32 jgraham: don't have the reverse: does fixing a test fix web compat 03:15:10 jgraham: data exists that building up internal understanding of when it's important 03:15:27 jgraham: things that are different between firefox and safari removes some objections 03:15:46 jgraham: or chrome and safari. firefox-specific failures 03:16:13 jgraham: have better ways to tell if a failure is important, is valuable to us 03:16:35 jgraham: we still don't understand how given a test failure impacts web compat 03:17:12 JohnJansen: if we reduce a site bug and fix that, then track back to which tests now pass 03:17:16 JohnJansen: but not reverse 03:17:35 JohnJansen: interaction between features also 03:17:57 jgraham: we could test that, but don't test all possible intersections 03:18:33 jgraham: reducing things that go into the suite 03:18:51 foolip: beyond harness errors, can we talk about flaky tests? 03:18:56 jgraham: infra has improved 03:19:17 denis_ has joined #testing 03:20:23 jgraham: some ideas that we havent' followed up 03:20:58 jgraham: if we can get to a situation where a library works around a browser bug, if they also file a browser bug 03:21:03 jgraham: would be impactful 03:21:18 foolip: triage metadata and bug linking, if there's labeling and start counts 03:21:52 foolip: test to spec linking. bikeshed and respec have something! 03:23:40 jgraham: progress, but relevant people aren't in the room 03:23:47 jgraham: test coverage 03:24:13 Hexcles: in blink we have coverage comparison between wpt and legacy layout tests 03:24:20 Hexcles: results are pretty good overall 03:24:41 lukebjerring: 10% difference between running all tests (wpt+layout) and only running wpt 03:25:06 lukebjerring: identify low hanging fruit to upstream tests to wpt 03:25:08 https://storage.googleapis.com/blink-wpt-coverage/201812/index.html 03:25:34 Hexcles: we can easily measure coverage data 03:25:49 Hexcles: i think there's effort to collect data on ongoing basis 03:25:59 whsieh has joined #testing 03:26:03 JohnJansen: region coverage? 03:26:09 JohnJansen: what does it mean? 03:26:16 gsnedders: basic blocks 03:27:07 jgraham: for gecko we have a coverage metric 03:27:12 Tootip is "Region coverage is the percentage of code regions which have been executed at least once. A code region may span multiple lines (e.g in a large function body with no control flow). However, it's also possible for a single line to contain multiple code regions (e.g in 'return x || y && z')." 03:27:18 jgraham: daily coverage runs maybe 03:27:34 jgraham: can see per testsuite 03:27:41 RRSAgent: make minutes, please 03:27:41 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html ato 03:27:44 jgraham: the UI doesn't yet display diffs between testsuites 03:27:53 jgraham: I have some of that data for gecko 03:28:04 ScribeNick: zcorpan 03:28:05 jgraham: some bits are better covered by mochitests, like gamepad 03:28:18 jgraham: some areas where wpt has better coverage 03:28:19 RRSAgent: make minutes 03:28:19 I have made the request to generate https://www.w3.org/2019/09/16-testing-minutes.html ato 03:28:37 Hexcles: one thing stood out 03:28:44 Hexcles: accessibility is poorly tested in wpt 03:28:48 gsnedders: not possible to test 03:29:09 jgraham: coverage is a way to identify places where wpt is weak 03:29:20 jgraham: might not always be fixable (like maybe GC) 03:29:35 jgraham: gamepad or accessibility should be testable 03:29:52 foolip: that's test automation 03:30:07 foolip: has coverage improved? 03:30:17 <_11> _11 has joined #testing 03:30:33 MikeSmith: how many tests do we have that are using ??? 03:30:44 MikeSmith: cases manual tests are converted 03:31:05 MikeSmith: incentive to groups to automate manual tests 03:31:16 MikeSmith: awareness, people don't know this is available 03:31:23 s/???/testdriver.js 03:31:28 foolip: 400 files testdriver.js 03:32:08 jgraham: automating stuff that we can't currently automate... some success 03:32:19 ato: in terms of testability extensions of webdriver api 03:32:30 ato: we've seen other specs e.g. permissions, write extensions 03:32:43 ato: but no implementations 03:32:58 foolip: generate test report has been implemented 03:33:29 jgraham: gecko hasn't implemented that yet 03:33:51 foolip: ~200 files testdriver.js a year ago 03:34:14 foolip: pointer events, painful? 03:34:34 NavidZ_: let anyone add switch to testdriver protocol 03:34:42 NavidZ_: gives user activation to the page 03:34:51 NavidZ_: nobody can do that 03:35:05 NavidZ_: one way to ask the test author to click or something 03:35:19 NavidZ_: question is, how much of this do we want to expose to the testers 03:35:32 NavidZ_: not testing parts of the browser 03:35:42 NavidZ_: some apis already that can expose that 03:35:53 NavidZ_: if we want to go down that path, do it all the way 03:36:03 NavidZ_: on windows, behaves differently than linux on mac 03:36:22 NavidZ_: chromium tests only, test can choose based on platform 03:36:32 NavidZ_: do we want to expose that in testdriver? 03:36:51 NavidZ_: focus next: can't get that without user interaction. difference between platforms 03:37:31 NavidZ_: adding automation for specific things, expose more and more of inner workings of the browser 03:37:49 foolip: do we want to add API for create user interaction defined in html? 03:37:58 ato: big discussion in browser testing and tools 03:38:14 Hexcles has joined #testing 03:38:18