Stale intents

[Dru Knox]

Hi all,

The following two intents are getting fairly old without API owner LGTM:

10/4/2016	Brett Wilson	Implement and ship	Disallow some invalid characters from URL host names	< LGTM x3
10/17/2016	Dave Tapuska	Ship	Intervene: Document Level Passive Event Listeners	< LGTM x3

The second intent, in particular, asked again for API owner feedback a week ago. Is there anything outstanding before we can provide additional feedback?

Thanks!

-Dru

[Chris Harrelson]

Dave's intent was blocked on better spec'ing and engagement with other browsers.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAJcfO46ASQTeZHtvXzL02xtrrbrThLMmGUbromoDG85QiYttag%40mail.gmail.com.

[Ojan Vafai]

He's followed up that he's done enough to upload the pull requests for changes to the DOM and TouchEvents specs. There's still some discussion going on with Anne, but not at a pace that would get in time for the m56 branch point.

My 2 cents is that we should ship aggressively in cases like this where there is large and immediate user visible benefit. The de facto practice of browsers for the past 20 years has been to ship these sorts of changes without discussing them with other vendors. We've gone above and beyond that by setting up a shared forum for these discussions, discussing this issue in a shared forum, and uploading pull requests for spec changes.

It's possible, but unlikely, that after the branch point there will be some significant feedback that would cause us to be uncomfortable shipping this change. In that case, the worst that would happen is we'd have to merge a change into the m56 branch turning off the flag. Given that, it would be a shame to wait an extra 2 months just because of some uncertainty.

On Wed, Nov 9, 2016 at 9:23 AM Chris Harrelson <chri...@chromium.org> wrote:

Dave's intent was blocked on better spec'ing and engagement with other browsers.

On Tue, Nov 8, 2016 at 4:31 PM, Dru Knox <dk...@chromium.org> wrote:

Hi all,

The following two intents are getting fairly old without API owner LGTM:

10/4/2016	Brett Wilson	Implement and ship	Disallow some invalid characters from URL host names	< LGTM x3
10/17/2016	Dave Tapuska	Ship	Intervene: Document Level Passive Event Listeners	< LGTM x3

The second intent, in particular, asked again for API owner feedback a week ago. Is there anything outstanding before we can provide additional feedback?

Thanks!

-Dru

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAJcfO46ASQTeZHtvXzL02xtrrbrThLMmGUbromoDG85QiYttag%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To post to this group, send email to blink-api-ow...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAOMQ%2Bw8C0SzhwULyKQxyn5PYkyXm4kW36w0SROjV4Yyw3jh6fA%40mail.gmail.com.

[Philip Jägenstedt]

The most important question in my mind, is if any other vendor is interested in implementing this. And related, if Chrome ships this and it sticks, can we have some confidence that roughly this behavior will make it into whichever specs are necessary, so that it doesn't end up an undocumented quirk of the platform. At the end of the day the WHATWG currently operates by "match implementation even if silly" so it's not really Anne that needs convincing. I've poked https://github.com/whatwg/dom/issues/365 yesterday.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CANMdWTuVBBu6g0EyEc0Dg9JqYDi3kwZG_i%3DNrG%3DeJhJe%3DbOvkw%40mail.gmail.com.

[Rick Byers]

[+dtapuska]

Honestly I don't think we're going to know that (regardless of what other vendors say) until the rubber really hits the road.  There is going to be some compat impact, many affected sites will update, a few won't.  Where other vendors draw the line here they likely can't predict up front.

To me the risk here is mitigated by the fact that we can likely un-ship this in the future without breaking anyone.  So if this fails to get implementation support with all the data we can provide on the tradeoff, we can still choose to prioritize predictability over the user experience.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAJcfO46ASQTeZHtvXzL02xtrrbrThLMmGUbromoDG85QiYttag%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAOMQ%2Bw8C0SzhwULyKQxyn5PYkyXm4kW36w0SROjV4Yyw3jh6fA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CANMdWTuVBBu6g0EyEc0Dg9JqYDi3kwZG_i%3DNrG%3DeJhJe%3DbOvkw%40mail.gmail.com.

--

You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-discuss+unsub...@chromium.org.
To post to this group, send email to blink-api-owners-discuss@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAARdPYftfrxXUxMnGWBoXKfK92uJtuUqdH7HpNgpnELDkDHwzA%40mail.gmail.com.