01:28:42 RRSAgent has joined #browserext 01:28:42 logging to http://www.w3.org/2017/02/16-browserext-irc 01:29:10 Zakim has joined #browserext 01:29:19 Meeting: Browser Extension CG teleconf 01:29:27 ScribeNick: Florian 01:29:33 Chair: Florian 01:29:38 scottlow has joined #browserext 01:29:45 Agenda: https://lists.w3.org/Archives/Public/public-browserext/2017Feb/0003.html 01:29:49 present+ mikepie 01:30:09 present+ 01:30:11 present+ Florian 01:30:19 present+ 01:30:45 present+ 01:32:51 Topic: * Status update and issue resolution on https://browserext.github.io/browserext/ 01:33:14 mikepie: I haven't had a chance to go through the IDs questions yet 01:33:36 mikepie: But other than what we have on the call today that's the only thing left, so we'll look into it 01:34:15 mikepie: on issue 15, we're past the 10 days after resolution, so we can close 01:35:17 mikepie: Next issue, we had already specified that the object returned by webdriver's getBrowserExtension method had an id, and I also specified that it should have the nae 01:35:19 name 01:35:30 kmag: This needs to be localized 01:35:54 kmag: Not sure which locale to use though 01:36:04 Florian: This is a setting that is often wrong 01:37:06 kmag: if we want to match the browser's UI locale, we need to expose that 01:37:22 Florian: In some cases you may want to match the site rather than the UI 01:38:25 scottlow: since the ID is an inpredictable number, you need a name to be able to know which extension your talking to 01:38:45 Florian: If that's what its for, it doesn't need localization, it needs predictability 01:38:53 mike: so we can use the default locale 01:39:11 RESOLUTION: Add the name property, and define it to be the default locale 01:39:27 ^ that was issue 31 01:39:46 mikepie: Issue 46: This is about interacting with permission prompts 01:40:01 mikepie: I made 3 additions 01:41:38 mikepie: the API lets you get the localized text of the permission prompt, and based on it accept it or dismiss it 01:42:00 kmag: I'm worried about text matching. 01:42:52 florian: what options do we have 01:43:12 kmag: we have an permission name string, and return that in json 01:43:36 kmag: these names are already standard 01:44:19 requestingUrl 01:44:27 mikepie: I'll replace that string with a JSON object, including "requestingUrl"... 01:44:48 mikepie: Also "permissions" 01:44:53 Florian: Why plural? 01:45:54 kmag: I think there can be multiple permissions in one dialog 01:46:38 mikepie: Yes, at install time, an extension can ask for multiple permission 01:47:19 scottlow: are these optional permissions? 01:47:49 kmag: in our case, geolocation is a bit special, but otherwise yes 01:48:07 scottlow: are these about security permissions as well? 01:48:17 kmag: no 01:48:36 scottlow has joined #browserext 01:49:09 Florian: We will deal with run-time permissions with this as well? 01:49:26 Florian: what if there's multiple ones queued up 01:50:22 kmag: you would have to accept or dismiss them in the order they are being displayed at. You cannot get the list of all queued permissions at once 01:52:03 Florian: Don't we have a risk to make author depends on browser specific ordering of the permission prompts 01:52:15 kmag: you do, but that's the sanest thing we can do anyway. 01:53:29 kmag: this can only happen if requesting multiple permissions at the same time 01:53:58 Florian: Yeah, this isn't great, as we may get authors to depend on the ordering even though they shouldn't, but I cannot think of a better alternative 01:54:05 mikepie: I'll add a note to call it out 01:54:53 mikepie: and the third property is the prompt text 01:55:53 Resolution: add requestingURL, permissions and promptText 01:56:18 resolution: the name of the method is getBrowserPermission (without Text) 01:56:54 kmag: we should also return a list of possible actions, such as "accept for session" in addition to just "accept" and "dismiss" 01:57:19 mikepie: Yes, I can add that. I like it. 01:58:28 RESOLUTION: add "actions", which must include "accept" and "dismiss", and and possibly other actions as available 01:58:50 Florian: we need to come of with name for these 01:58:57 s/name/names/ 02:00:14 mikepie: This is also something you'd want to handled declaratively 02:00:20 kmag: that worries me 02:02:00 kmag: I think the default one should not be "dismiss" temporarily, it should be "deny" 02:02:46 mike: this should be for the session, right? 02:02:58 mikepie: with webdriver, the install are just for the session 02:03:10 mandatory: accept; deny (for session? permanent?) 02:04:42 mikepie: session and permanent is the same, since the extension is only installed for the session 02:04:51 Florian: right, but deny and dismiss are different 02:05:05 kmag: and we should go with deny rather than dismiss as the mandatory one 02:05:23 RESOLUTION: replace dismiss with deny 02:06:30 Florian: do we need to come up with names? 02:06:54 mikepie: since there's not difference between permanent and for this session only, allow, deny and dismiss are all we need 02:08:45 Florian: so we only have 2 possible cases at install time, and 3 at run time 02:08:59 kmag: at install time, the only choise is really install extension or not 02:09:11 mikepie: I'll add a session to explain what kind of thing can appear there 02:11:04 Florian: if there can be other names, do we need to standardize? 02:11:09 all: yes, but not now. 02:14:03 Florian: mikepie, you can merge the PR once the changes are in 02:14:10 Topic: Next meeting 02:14:24 mikepie: How about the ides of March 02:15:18 all: agreed. 02:20:25 RRSAgent, make log public 02:20:32 RRSAgent, draft minutes 02:20:32 I have made the request to generate http://www.w3.org/2017/02/16-browserext-minutes.html Florian 02:22:48 RRSAgent, bye 02:22:48 I see no action items