Updated the chromestatus to 127-132, thanks!
On Wed, May 29, 2024 at 7:58 AM Vladimir Levin wrote:
>
>
> On Wed, May 29, 2024 at 10:47 AM Daniel Bratell
> wrote:
>
>> That is 7 milestones.
>>
>> End at 132 inclusive instead?
>>
> Oops, off-by-one strikes again!
>
> Yes, 132 inclusive is the
On Wed, May 29, 2024 at 10:47 AM Daniel Bratell wrote:
> That is 7 milestones.
>
> End at 132 inclusive instead?
>
Oops, off-by-one strikes again!
Yes, 132 inclusive is the right endpoint
> /Daniel
> On 2024-05-28 18:58, Vladimir Levin wrote:
>
> LGTM to experiment from 127 to 133 inclusive
>
That is 7 milestones.
End at 132 inclusive instead?
/Daniel
On 2024-05-28 18:58, Vladimir Levin wrote:
LGTM to experiment from 127 to 133 inclusive
On Tue, May 28, 2024 at 12:54 PM Di Zhang wrote:
Thanks Mike. Your explanation makes sense and we are good with 6
milestones to start.
LGTM to experiment from 127 to 133 inclusive
On Tue, May 28, 2024 at 12:54 PM Di Zhang wrote:
> Thanks Mike. Your explanation makes sense and we are good with 6
> milestones to start.
> We expect the deprecation trial period to be longer to give web users
> enough time to adjust, but can
Thanks Mike. Your explanation makes sense and we are good with 6 milestones
to start.
We expect the deprecation trial period to be longer to give web users
enough time to adjust, but can request a renewal when the time comes.
I have updated the Origin Trial period to start on 127 and end on
Thanks Di - this is a useful clarification.
You can request up to 6 milestones for a Deprecation Trial, and only
need a single LGTM. Renewals are possible, with sufficient justification.
That said, if you do think that 9 milestones is sufficient for your
needs - that is also possible, but
Sorry for missing information! I haven’t created a request for a
Deprecation Trial before, which is what I intended this to be, and I missed
some parts of the process. The chromestatus is located here, which is for
the overall KeyboardFocusableScrollers feature:
On Fri, May 10, 2024 at 2:18 PM Mike Taylor wrote:
> Is there a chromestatus entry associated with this intent? There's a lot
> of information missing from this Intent (see
> https://groups.google.com/a/chromium.org/g/blink-dev/c/LwgSKPBivuM/m/0dRsXWhBAgAJ
> as what is typical) - could you reply
Is there a chromestatus entry associated with this intent? There's a lot
of information missing from this Intent (see
https://groups.google.com/a/chromium.org/g/blink-dev/c/LwgSKPBivuM/m/0dRsXWhBAgAJ
as what is typical) - could you reply with the missing info?
(Did you use ChromeStatus to
Contact emails
dizha...@chromium.org
dom-...@google.com
*Experiment Goals*The feature KeyboardFocusableScrollers changes the
focusability of a a scroll container. This is an important improvement to
help make scrollers and contents within scrollers more accessible to all
users. The goal of
10 matches
Mail list logo
