blink-dev -> bcc
+headless-dev@
Hi Todd,
On Wed, May 4, 2022 at 11:31 AM Todd Wilder wrote:
> I have no desire to layout or paint anything in my headless use case, and
> i'm going through the code base, tracing and then commenting out
> layout/paint methods, testing, etc. Its a difficult proces
M103.
I will be sure to let you know if that changes for some reason.
Thanks!
On Wed, May 4, 2022 at 12:08 PM 'Joe Medley' via blink-dev <
blink-dev@chromium.org> wrote:
> In which version are you wanting to ship?
>
> On Wednesday, May 4, 2022 at 6:06:30 AM UTC-7 mkwst via Chromestatus wrote:
>
I have no desire to layout or paint anything in my headless use case, and
i'm going through the code base, tracing and then commenting out
layout/paint methods, testing, etc. Its a difficult process. Can anyone
recommend an easy way to "disable" layout, styling and painting?
--
You received th
The API owners met today and discussed this Intent.
Overall, I'd summarize as saying that I think the API owners would only be
comfortable extending the origin trial by 3 milestones at this time. (We
have not yet approved that extension however; first I'd like to wait for an
answer to the followup
In which version are you wanting to ship?
On Wednesday, May 4, 2022 at 6:06:30 AM UTC-7 mkwst via Chromestatus wrote:
> LGTM3.
>
--
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, sen
Ok. LGTM to experiment from M102 to M104.
On Wed, May 4, 2022 at 7:15 AM Shivani Sharma
wrote:
>
>
> On Wed, May 4, 2022 at 9:11 AM Mike West wrote:
>
>> On Monday, May 2, 2022 at 8:48:53 PM UTC+2 Shivani Sharma wrote:
>>
>>> Thanks Yoav!
>>>
>>> On Mon, May 2, 2022 at 7:27 AM Yoav Weiss
>>> w
LGTM3
On Wed, May 4, 2022 at 8:45 AM Yoav Weiss wrote:
> LGTM2
>
> On Wednesday, May 4, 2022 at 5:44:20 PM UTC+2 slightlyoff via Chromestatus
> wrote:
>
>> LGTM1
>>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this gr
LGTM2
On Wednesday, May 4, 2022 at 5:44:20 PM UTC+2 slightlyoff via Chromestatus
wrote:
> LGTM1
>
--
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+unsub
LGTM1
--
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+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chro
Microsoft would like to see this ship ASAP. LGTM1
--
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+unsubscr...@chromium.org.
To view this discussion on the
I LGTM'd in the tool but it didn't show up here, but y'all have my +1.
Thanks for getting this done.
On Thursday, April 28, 2022 at 5:01:51 PM UTC-7 Joshua Bell wrote:
> FYI, non-normative note added. I also followed up on the questions in the
> Moz standards position thread, added a few more n
Is Google scoping the OT to just US and English browsers?
Will the FLEDGE option be in all translations of Chrome 101 and above?
--
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
When Google ends FLEDGE OT, what will that process be or look like?
Will the FLEDGE options be removed from Chrome?
What options to developers have if they want to have their OT extend into
September to gather data for their development?
--
You received this message because you are subscribed to
> In the long term, we expect this change to improve compatibility, as UA
detection based on UA-CH is bound to be more reliable than the current
status quo.
Data so far suggests that this is not in fact the case due to model name
collisions e.g. X1, A1 etc. See
https://github.com/WICG/ua-clie
Thanks for the review Yoav. Responses inline.
On Wed, May 4, 2022 at 6:12 AM Yoav Weiss wrote:
>
>
> On Monday, May 2, 2022 at 11:52:56 PM UTC+2 Khushal Sagar wrote:
>
>> Contact emailskhushalsa...@chromium.org
>>
>> Explainer
>> https://github.com/WICG/shared-element-transitions/blob/main/overf
On Wed, May 4, 2022 at 9:11 AM Mike West wrote:
> On Monday, May 2, 2022 at 8:48:53 PM UTC+2 Shivani Sharma wrote:
>
>> Thanks Yoav!
>>
>> On Mon, May 2, 2022 at 7:27 AM Yoav Weiss wrote:
>>
>>>
>>>
>>> On Sat, Apr 30, 2022 at 12:31 AM Shivani Sharma
>>> wrote:
>>>
Contact emails
On Monday, May 2, 2022 at 8:48:53 PM UTC+2 Shivani Sharma wrote:
> Thanks Yoav!
>
> On Mon, May 2, 2022 at 7:27 AM Yoav Weiss wrote:
>
>>
>>
>> On Sat, Apr 30, 2022 at 12:31 AM Shivani Sharma
>> wrote:
>>
>>> Contact emails
>>>
>>> shivani...@chromium.org, d...@chromium.org, jkar...@chromium.or
LGTM3.
--
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+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chr
LGTM3.
--
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+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chr
Great suggestion Yoav!
Let's agree to extend the OT for now until M109 (6x MS) and I'll report
back as soon as we've a clearer timeline.
Does that work for other API owners as well?
On Wed, May 4, 2022 at 12:26 PM Yoav Weiss wrote:
> It seems appropriate to keep the Deprecation Trial until we s
It seems appropriate to keep the Deprecation Trial until we shipped
alternatives, but I tend to agree with Chris that 10 milestones sounds like
a lot. Maybe we can renew the Deprecation Trial for 6 milestones (till
M109), and revisit that once it's close to expiry?
On Tuesday, May 3, 2022 at 12
On Monday, May 2, 2022 at 11:52:56 PM UTC+2 Khushal Sagar wrote:
> Contact emailskhushalsa...@chromium.org
>
> Explainer
> https://github.com/WICG/shared-element-transitions/blob/main/overflow_on_replaced_elements.md
>
> Specificationhttps://drafts.csswg.org/css-overflow/#overflow-clip-margin
>
On Wednesday, May 4, 2022 at 1:08:11 AM UTC+2 Joey Arhar wrote:
> Contact emailsjar...@chromium.org
>
> Explainer
> https://github.com/WICG/display-locking/blob/main/explainers/isvisible.md
>
> Specificationhttps://drafts.csswg.org/cssom-view/#dom-element-isvisible
>
> Summary
>
> Element.isVisi
LGTM2
On Wed, May 4, 2022 at 11:48 AM Daniel Bratell wrote:
> LGTM1
>
> The only tangible risk I can think of is that there are sites that depend
> on opener but has rel=noopener in their form element. It seems unlikely and
> considering it's already shipped in WebKit, I think this is fine.
>
>
LGTM1
The only tangible risk I can think of is that there are sites that
depend on opener but has rel=noopener in their form element. It seems
unlikely and considering it's already shipped in WebKit, I think this is
fine.
/Daniel
On 2022-05-03 19:17, Joey Arhar wrote:
Contact ema
LGTM2
/Daniel
On 2022-05-03 16:23, Yoav Weiss wrote:
LGTM1
Thanks for aligning with the spec and tackling this change carefully.
Hoping it sticks.
On Tue, May 3, 2022 at 4:18 PM Matt Reichhoff
wrote:
Contact emails
mreichh...@chromium.org, miketa...@chromium.org
26 matches
Mail list logo
