Re: Telecon / meeting on first week of April for Web Components

2016-04-05 Thread Jan Miksovsky
Thanks to everyone who participated in the call. (Special thanks to those 
calling from Tokyo!)

Minutes for the meeting are at 
https://www.w3.org/2016/04/05-webapps-minutes.html 
.

Re: Telecon / meeting on first week of April for Web Components

2016-04-05 Thread Anne van Kesteren
On Tue, Apr 5, 2016 at 6:55 PM, Xiaoqian Wu  wrote:
> I’m unfamiliar with WebEx. If Chaals or someone wants to make a strong push
> to use that, please set up the call and send out instructions for joining.

FYI: we're using Hangouts. If anyone cannot join please tell us on IRC
(#webapps, W3C IRC).


-- 
https://annevankesteren.nl/



Re: Telecon / meeting on first week of April for Web Components

2016-04-05 Thread Xiaoqian Wu

> On 6 Apr 2016, at 12:29 AM, Jan Miksovsky  wrote:
> 
> I’m unfamiliar with WebEx. If Chaals or someone wants to make a strong push 
> to use that, please set up the call and send out instructions for joining.

We’ve scheduled a WebEx call for this Telecon, in case you will need it.

-
Web Components
Tuesday, April 5, 2016
10:00 am  |  Pacific Daylight Time (San Francisco, GMT-07:00)  |  2 hrs
 
Join WebEx meeting
Link: https://mit.webex.com/mit/j.php?MTID=m6515c79ee5dca2d7b6fd3a07a4dd160a
Meeting number: 643 198 155
Meeting password:   webplatform
 
Join by phone
+1-617-324- US Toll Number
Access code: 643 198 155
Mobile Auto Dial:+1-617-324-,,,643198155#

--

Please feel free to use Google Hangouts if that works better for most of you. 
Have fun.

-xiaoqian

> 
> Baring that, I propose the default meeting location is on Google Hangouts: 
> https://hangouts.google.com/call/rwiluf6hlbhkzf4566hq4biedye 
> . If we go 
> ahead with Hangouts and Chaals can’t join, I’ll volunteer to act as scribe, 
> at least for the beginning.
> 
> I’m on the IRC channel gave (irc://irc.w3.org/#public-webapps 
> ) if anyone wants to discuss pre-call 
> logistics.
> 
> As a reminder: the proposed agenda for the meeting is to go through the 
> “needs consensus” items posted at 
> https://github.com/w3c/webcomponents/issues?q=is%3Aissue+is%3Aopen+label%3A%22needs+consensus%22
>  
> .
>  It sounds like it would be good to resolve pending Shadow DOM issues before 
> tackling Custom Elements issues.



RE: Telecon / meeting on first week of April for Web Components

2016-04-05 Thread Domenic Denicola
From: Jan Miksovsky [mailto:jan@component.kitchen] 

> As a reminder: the proposed agenda for the meeting is to go through the 
> “needs consensus” items posted at 
> https://github.com/w3c/webcomponents/issues?q=is:issue+is:open+label:"needs+consensus;.
>  It sounds like it would be good to resolve pending Shadow DOM issues before 
> tackling Custom Elements issues.

I spent some time organizing these "needs consensus" issues into a 
category/priority list. Let's try to go in this order (which interleaves SD and 
CE):

## Definitely needs discussion

* [SD] https://github.com/w3c/webcomponents/issues/308: should we use `display: 
contents`
* [CE] https://github.com/w3c/webcomponents/issues/417: caching vs. late 
binding of lifecycle callbacks

## Discussion would be good; still contentious/tricky

* [SD] https://github.com/w3c/webcomponents/issues/477: 
`document.currentScript` censoring
* [SD] https://github.com/w3c/webcomponents/issues/355: use CSS containment 
features by default
* [CE] https://github.com/w3c/webcomponents/issues/186: integrating callback 
invocation with IDL and editing operations

## New feature proposals

* [CE] https://github.com/w3c/webcomponents/issues/468: provide a mechanism for 
adding default/"UA" styles to a custom element
* [SD] https://github.com/w3c/webcomponents/issues/288: `slotchange` event

## Discussion would be good, but there's likely a default consensus based on 
GitHub discussions so far

* [SD] https://github.com/w3c/webcomponents/issues/59: parse `` like 
``
* [Both] https://github.com/w3c/webcomponents/issues/449: restrict to secure 
contexts
* [CE] https://github.com/w3c/webcomponents/issues/474: define order for 
attributeChangedCallback invocations

## Bikeshedding; probably does not need telecom time

* [SD] https://github.com/w3c/webcomponents/issues/451: rename getAssignedNodes 
and assignedSlot
* [CE] https://github.com/w3c/webcomponents/issues/434: rename "custom tag" and 
"type extension"

See you all in a few!


Re: Telecon / meeting on first week of April for Web Components

2016-04-05 Thread Jan Miksovsky
I’m unfamiliar with WebEx. If Chaals or someone wants to make a strong push to 
use that, please set up the call and send out instructions for joining.

Baring that, I propose the default meeting location is on Google Hangouts: 
https://hangouts.google.com/call/rwiluf6hlbhkzf4566hq4biedye 
. If we go ahead 
with Hangouts and Chaals can’t join, I’ll volunteer to act as scribe, at least 
for the beginning.

I’m on the IRC channel gave (irc://irc.w3.org/#public-webapps 
) if anyone wants to discuss pre-call 
logistics.

As a reminder: the proposed agenda for the meeting is to go through the “needs 
consensus” items posted at 
https://github.com/w3c/webcomponents/issues?q=is%3Aissue+is%3Aopen+label%3A%22needs+consensus%22
 
.
 It sounds like it would be good to resolve pending Shadow DOM issues before 
tackling Custom Elements issues.

Re: [Push API] Fine-grained unsubscription

2016-04-05 Thread Marco Colli
If you show some pieces of information to the user when he allows the
notifications he won't remember that when he unsubscribes.

However the point really is to remember to the user that he can turn off
some notifications through the website and not necessarily all. This is
exactly how it works for emails. When you click the "Unsubscribe" link many
times you have the option to unsubscribe only partially.

2016-04-04 23:40 GMT+02:00 Jonathan Garbee :

> I come across the "Are You Sure?" when unsubscribing from email lists a
> lot. I don't think it is something we should allow, it is annoying and
> sounds condescending to people. I'm making a choice to press this thing, i
> mean it.
>
> I think it is best if sites simply offer notification preferences in their
> settings and when a user initially allows for notifications then you alert
> them that the preferences exist to control which ones you send.
>
> I think what is currently offered is right, if the user chooses to
> opt-out, just let them without friction. It is up to sites to not spam
> users with unwanted notifications anyways, not for users to prune what
> types they see to not be notified as much.
>
> On Mon, Apr 4, 2016 at 3:39 PM Marco Colli  wrote:
>
>> Currently the user can turn off notifications for a website directly from
>> the browser. When he unsubscribes all notifications from that website are
>> turned off.
>>
>> However, it is a common practice (for example with email) to allow the
>> user to turn off only some topics (i.e. fine grained preferences). I think
>> this is a must for push notifications too.
>>
>> A simple way to implement this would be to add an editPreferencesUrl
>> option to the pushManager.subscribe(). Then, when the user clicks the wheel
>> to turn off push notifications sees two options: "Turn off all
>> notifications" and "Manage push preferences on the website". When he clicks
>> the latter is sent to the editPreferencesUrl on the website.
>>
>> It would also be very useful to be able to display a custom message
>> before the unsubscription happens. That message can appear above the
>> unsubscribe actions.
>>
>> Another option would be to have a callback *before* the unsubscription:
>> that callback can show a single prompt to the user with a custom message
>> (e.g. "Are you sure? Remember that you can visit example.com if you want
>> to turn off only some notifications").
>>
>>
>> Marco Colli
>> Pushpad (https://pushpad.xyz)
>>
>


Re: [Push API] Fine-grained unsubscription

2016-04-05 Thread Martin Thomson
On 4 April 2016 at 16:34, Marco Colli  wrote:
> A simple way to implement this would be to add an editPreferencesUrl option
> to the pushManager.subscribe(). Then, when the user clicks the wheel to turn
> off push notifications sees two options: "Turn off all notifications" and
> "Manage push preferences on the website". When he clicks the latter is sent
> to the editPreferencesUrl on the website.

This is really something that you want to take up with browser
vendors.  In that regard, I can only tell you that developing UI
around these features is very difficult.



Re: Telecon / meeting on first week of April for Web Components

2016-04-05 Thread Michael[tm] Smith
Anne van Kesteren , 2016-04-05 07:10 +0200:
> Archived-At: 
> 
> 
> On Tue, Apr 5, 2016 at 12:19 AM, Jan Miksovsky  wrote:
> > I have no idea how to settle this question. If everyone else is happy using 
> > WebEx, and someone else can set up the video call, I certainly don’t have a 
> > problem with that. (My only issue would be if the meeting was restricted to 
> > voice only.)
> 
> Does WebEx even support video?

It does

> In any event, per
> https://www.w3.org/2006/tools/wiki/InstallingWebEx this would require
> Java, which is a major security risk, and it seems the fallback is
> audio-only.

FWIW, there is an Android client (including video support). That is what I
use personally, though the only thing I use it for is it get the webex
system to call me back to dial me in to the conference on audio. After I
get that audio connection I then just shut down the client.

> So it seems better to use Hangouts or some such.

Yeah, if everybody can agree to that it may work out a lot better.

But another option is to use a WebRTC service like https://appear.in/ which
work well enough these days with up to 8 video connections going at once.

  —Mike

-- 
Michael[tm] Smith https://people.w3.org/mike


signature.asc
Description: PGP signature