Fwd: [blink-dev] Intent to Ship: Scroll Anchoring

14 views
Skip to first unread message

Chris Harrelson

unread,
Nov 11, 2016, 8:27:59 PM11/11/16
to blink-api-owners-discuss
AIUI this intent requires a CSS change (the "overflow-anchor" property). I can't find any CSS draft spec that includes it.
It appears to only be in the scroll anchoring draft spec. Any other opinions on whether this is problematic?

Chris

---------- Forwarded message ----------
From: Philip Jägenstedt <foo...@chromium.org>
Date: Fri, Nov 11, 2016 at 10:37 AM
Subject: Re: [blink-dev] Intent to Ship: Scroll Anchoring
To: Steve Kobes <sko...@chromium.org>
Cc: Rick Byers <rby...@chromium.org>, Chris Harrelson <chri...@chromium.org>, Dimitri Glazkov <dgla...@chromium.org>, blink-dev <blin...@chromium.org>, oj...@chromium.org


No need, I just wasn't sure if you wanted to wait. LGTM2.

On Fri, Nov 11, 2016 at 6:21 PM Steve Kobes <sko...@chromium.org> wrote:
We'd like to ship now (hence the intent).  But if the decision of the API owners is that we need more feedback from vendors before shipping, then we'll wait for that.

On Fri, Nov 11, 2016 at 1:21 AM, Philip Jägenstedt <foo...@chromium.org> wrote:
To be explicit, would you like to go ahead with shipping this now, or will you get back to this thread when you have some feedback from other vendors?

On Thu, Nov 10, 2016 at 8:00 PM Steve Kobes <sko...@chromium.org> wrote:
On Thu, Nov 10, 2016 at 6:38 AM, Philip Jägenstedt <foo...@chromium.org> wrote:
Have you reached out to other vendors outside of https://github.com/WICG/interventions/issues/2? David Baron seems positive, but an explicit "we're going to ship this, what do you think?" would be nice, if it hasn't already happened.

We're in the process of doing this.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

Ojan Vafai

unread,
Nov 12, 2016, 2:06:01 AM11/12/16
to Chris Harrelson, blink-api-owners-discuss

We just have the spec at the wicg. The only real risk is someone objects to the names and values of the CSS property. We are hopeful that the actual anchoring algorithm, which is where most of the complexity is, can still be changed in future versions of Chrome after we have shipped to stable.

We want to aim for m56 (which branched yesterday?), but if we get significant feedback from other browsers that would require not shipping in 56, we can still turn it off on the 56 branch in the coming weeks and ship in 57 instead.


To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
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%2Bw-MLDTo-rp2Rhz9cCCXvyO0W8qzxEmuNPMr%2BPuk7cwbgA%40mail.gmail.com.

Rick Byers

unread,
Nov 12, 2016, 2:05:30 PM11/12/16
to Ojan Vafai, L. David Baron, Chris Harrelson, blink-api-owners-discuss
Steve has asked for feedback, including filing an issue for CSSWG but we haven't heard anything concrete yet.  In general I don't think we should block shipping waiting for feedback (especially given how excited we know users are to see this improvement).  However it would be much better if we could at least have some "we're interested in exploring this too" signal so that we can move the repo to WICG and continue collaboration in the context of the W3C.

David, based on your comment would you be willing to chime in on the discourse thread about whether or not this proposal should move to WICG?  Separately, if you have time, we'd love to hear (here or on the intent thread) whether the initial proposal seems mature enough as a first start to try shipping in blink?

Thanks,
  Rick

On Fri, Nov 11, 2016 at 11:05 PM, Ojan Vafai <oj...@chromium.org> wrote:

We just have the spec at the wicg. The only real risk is someone objects to the names and values of the CSS property. We are hopeful that the actual anchoring algorithm, which is where most of the complexity is, can still be changed in future versions of Chrome after we have shipped to stable.

We want to aim for m56 (which branched yesterday?), but if we get significant feedback from other browsers that would require not shipping in 56, we can still turn it off on the 56 branch in the coming weeks and ship in 57 instead.

On Fri, Nov 11, 2016, 5:27 PM Chris Harrelson <chri...@chromium.org> wrote:
AIUI this intent requires a CSS change (the "overflow-anchor" property). I can't find any CSS draft spec that includes it.
It appears to only be in the scroll anchoring draft spec. Any other opinions on whether this is problematic?

Chris

---------- Forwarded message ----------
From: Philip Jägenstedt <foo...@chromium.org>
Date: Fri, Nov 11, 2016 at 10:37 AM
Subject: Re: [blink-dev] Intent to Ship: Scroll Anchoring
To: Steve Kobes <sko...@chromium.org>
Cc: Rick Byers <rby...@chromium.org>, Chris Harrelson <chri...@chromium.org>, Dimitri Glazkov <dgla...@chromium.org>, blink-dev <blin...@chromium.org>, oj...@chromium.org


No need, I just wasn't sure if you wanted to wait. LGTM2.

On Fri, Nov 11, 2016 at 6:21 PM Steve Kobes <sko...@chromium.org> wrote:
We'd like to ship now (hence the intent).  But if the decision of the API owners is that we need more feedback from vendors before shipping, then we'll wait for that.

On Fri, Nov 11, 2016 at 1:21 AM, Philip Jägenstedt <foo...@chromium.org> wrote:
To be explicit, would you like to go ahead with shipping this now, or will you get back to this thread when you have some feedback from other vendors?

On Thu, Nov 10, 2016 at 8:00 PM Steve Kobes <sko...@chromium.org> wrote:
On Thu, Nov 10, 2016 at 6:38 AM, Philip Jägenstedt <foo...@chromium.org> wrote:
Have you reached out to other vendors outside of https://github.com/WICG/interventions/issues/2? David Baron seems positive, but an explicit "we're going to ship this, what do you think?" would be nice, if it hasn't already happened.

We're in the process of doing this.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
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.

--
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/CANMdWTtwJW1BXL_Jopy2-0aQPEstXhAyOi6tfvcAkKgs2bV6TQ%40mail.gmail.com.

Rick Byers

unread,
Nov 14, 2016, 8:08:47 PM11/14/16
to Ojan Vafai, L. David Baron, Chris Harrelson, blink-api-owners-discuss
We haven't heard any feedback on this API yet and we're nearing the M56 branch point.  I think Ojan and Chris have done all the due diligence to ask for feedback in the right places.  I propose that we move ahead with plans to ship in M56.  Chrome 56 is slated to ship by end of January, so we've got about 2 months to either merge tweaks to the API or pull the plug on 56 if there are major concerns.  I don't think we gain much by waiting longer and missing the M56 branch.  Chris, WDYT?

Rick

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

--
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+unsubscr...@chromium.org.

To post to this group, send email to blink-api-owners-discuss@chromium.org.

Rick Byers

unread,
Nov 14, 2016, 8:09:25 PM11/14/16
to Ojan Vafai, L. David Baron, Chris Harrelson, blink-api-owners-discuss
On Mon, Nov 14, 2016 at 5:08 PM, Rick Byers <rby...@chromium.org> wrote:
We haven't heard any feedback on this API yet and we're nearing the M56 branch point.  I think Ojan and Chris have

Sorry, typo - should be "Steve and Ojan". 

Chris Harrelson

unread,
Nov 16, 2016, 12:31:58 PM11/16/16
to Rick Byers, Ojan Vafai, L. David Baron, blink-api-owners-discuss
LGTM3 to ship in M56, given that this is a really nice and important feature and we have in fact reached out repeatedly and in multiple ways.

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/CAFUtAY9-wO0OvksuO7GK9PX-CoyYm_GOZNgHBhxgxzwDXkoaYg%40mail.gmail.com.

Ojan Vafai

unread,
Nov 16, 2016, 12:50:31 PM11/16/16
to Chris Harrelson, Rick Byers, L. David Baron, blink-api-owners-discuss
To be fair, our most recent reaching out was more last minute than I'm happy with. But given that we have some time between now and 56 shipping to stable, there's still a fair amount of time for us to receive feedback before we're locked in.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
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.

--
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.

--
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/CAFUtAY9-wO0OvksuO7GK9PX-CoyYm_GOZNgHBhxgxzwDXkoaYg%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%2Bw9dFFW5GdqTTnzc-ARW5zjWCdML3A0-Evhyrt02DxVGVA%40mail.gmail.com.

Rick Byers

unread,
Nov 16, 2016, 1:15:37 PM11/16/16
to Ojan Vafai, Chris Harrelson, blink-api-owners-discuss, blink-dev
+blink-dev again now that some discussion has concluded and we have the required 3 LGTMs.  

LGTM4 FWIW

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
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.

--
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.

--
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.

--
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.

--
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/CANMdWTs5u9YG9Zndncawjct%2BXB8r%3DJn%2BU%3DSTqZwqDNt_9prBXA%40mail.gmail.com.

Steve Kobes

unread,
Nov 16, 2016, 2:38:35 PM11/16/16
to Rick Byers, Ojan Vafai, Chris Harrelson, blink-api-owners-discuss, blink-dev
Thanks everyone.  We'll proceed with launching in M56.

LGTM4 FWIW

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

--
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+unsubscr...@chromium.org.

To post to this group, send email to blink-api-owners-discuss@chromium.org.

--
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+unsubscr...@chromium.org.

To post to this group, send email to blink-api-owners-discuss@chromium.org.

--
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+unsubscr...@chromium.org.

--
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+unsubscr...@chromium.org.

To post to this group, send email to blink-api-owners-discuss@chromium.org.
Reply all
Reply to author
Forward
0 new messages