(sending this again, previous email was lacking template & details)
Primary eng (and PM) emails
nrosent...@chromium.org
mk...@chromium.org
Summary
Prefetch-src was never fully adopted, but was shipped by mistake in 2021
(the flag was removed, Oops)
We’ve since changed the spec, and the repl
LGTM0 (I'm recused, as this has my name on it).
For a little more color, we accidentally shipped `prefetch-src` in M92 when
moving CSP parsing out of the renderer. The check in
https://chromium-review.googlesource.com/c/chromium/src/+/2839603/8/third_party/blink/renderer/core/frame/csp/csp_directi
LGTM1 - as potential breakage won't be user visible and would be mitigated
by other means.
On Wed, Feb 8, 2023 at 11:21 AM Mike West wrote:
> LGTM0 (I'm recused, as this has my name on it).
>
> For a little more color, we accidentally shipped `prefetch-src` in M92
> when moving CSP parsing out o
On Tue, Feb 7, 2023 at 7:31 AM Koji Ishii wrote:
> Specification
> https://w3c.github.io/csswg-drafts/css-text-4/#valdef-text-wrap-balance
>
> Summary
>
> Enables the lengths of lines in a paragraph balanced, for better
> readability and to prevent typographic widows. This feature is often used
>
Any use counters on how often this happens?
On Thursday, February 2, 2023 at 8:58:35 AM UTC+1 Kenichi Ishibashi wrote:
Contact emailsba...@chromium.org
Specificationhttps://fetch.spec.whatwg.org/#http-redirect-fetch
Summary
Remove Authorization header on cross origin redirects to scope a
devel
Any use counters for when it is used?
On Saturday, February 4, 2023 at 12:46:16 AM UTC+1 Carlos IL wrote:
Contact emailscarlo...@chromium.org
ExplainerNone
Specificationhttps://www.w3.org/TR/mixed-content/#strict-checking
Summary
block-all-mixed-content is a CSP directive that causes Chrome to
On Tue, Feb 7, 2023 at 6:56 AM 'Jiacheng Guo' via blink-dev <
blink-dev@chromium.org> wrote:
> Contact emails...@google.com
>
> ExplainerThis is an implementation of an established standard.
>
> Specificationhttps://url.spec.whatwg.org/#concept-ipv6-parser
>
> Summary
>
> The behavior of parsing I
LGTM1
Thanks for aligning with the spec!
On Wed, Feb 8, 2023 at 1:35 AM Ken Russell wrote:
> Contact emails
>
> k...@chromium.org
>
> Explainer
>
> None
>
> Specification
>
> https://registry.khronos.org/webgl/specs/latest/1.0
>
> Summary
>
> The WebGLContextEvent type has been defined in Khron
LGTM2
On Wed, Feb 8, 2023 at 10:20 AM Yoav Weiss wrote:
> LGTM1
>
> Thanks for aligning with the spec!
>
> On Wed, Feb 8, 2023 at 1:35 AM Ken Russell wrote:
>
>> Contact emails
>>
>> k...@chromium.org
>>
>> Explainer
>>
>> None
>>
>> Specification
>>
>> https://registry.khronos.org/webgl/specs/
LGTM3
On Wed, Feb 8, 2023 at 8:19 AM Rick Byers wrote:
> LGTM2
>
> On Wed, Feb 8, 2023 at 10:20 AM Yoav Weiss wrote:
>
>> LGTM1
>>
>> Thanks for aligning with the spec!
>>
>> On Wed, Feb 8, 2023 at 1:35 AM Ken Russell wrote:
>>
>>> Contact emails
>>>
>>> k...@chromium.org
>>>
>>> Explainer
>>>
It sounds like the only potential concern is a security one - where content
previously blocked at the site's request was no longer blocked. Is that
right? If so then I'd defer to security reviewers and approve from a web
compat perspective without any metrics.
Rick
On Wed, Feb 8, 2023 at 10:01 AM
Feature detection will be possible using `@supports selector(&)`. Due to a
bug there was a false positive with the flag turned off, but that's been
fixed in https://bugs.chromium.org/p/chromium/issues/detail?id=1414012
today and a backport to 111 has been requested.
The false positive will remain
LGTM1 Do we know if other browsers that support offscreen canvas (Safari TP,
eg) handle this the same way? Or are we the first to ship?
--
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 i
LGTM2
On Wed, Feb 8, 2023 at 4:48 AM Yoav Weiss wrote:
> LGTM1 - as potential breakage won't be user visible and would be mitigated
> by other means.
>
> On Wed, Feb 8, 2023 at 11:21 AM Mike West wrote:
>
>> LGTM0 (I'm recused, as this has my name on it).
>>
>> For a little more color, we accid
Hi There,
Does anyone happen to know what's the status on this one..? Is it more like
an abandoned thread...?
Best,
- Lorand.
On Friday, April 29, 2022 at 8:29:29 PM UTC+3 Mahdi Hosseinzadeh wrote:
> One use case is how to replace the SMIL animations with CSS animations in
> markdown files?
>
Hi Lorand,
SMIL was not deprecated and there are no plans to do so. It's still a
supported feature in Chromium.
On Wed, Feb 8, 2023 at 9:02 AM Lorand Zudor wrote:
> Hi There,
>
> Does anyone happen to know what's the status on this one..? Is it more
> like an abandoned thread...?
>
> Best,
> -
LGTM3
/Daniel
On 2023-02-08 17:39, Chris Harrelson wrote:
LGTM2
On Wed, Feb 8, 2023 at 4:48 AM Yoav Weiss wrote:
LGTM1 - as potential breakage won't be user visible and would be
mitigated by other means.
On Wed, Feb 8, 2023 at 11:21 AM Mike West wrote:
LGTM0 (I'm recus
Proposal based on our meeting:
- Requesting to make this ENABLED_BY_DEFAULT in M112 but to have a Reverse
Origin Trial available with an end date date 3 milestones out: M115.
On Tuesday, February 7, 2023 at 10:19:35 PM UTC+1 Chris Thompson wrote:
> > Do we have trackable statistics on the usage
It sound like the user has already agreed to seeing "insecure" and
possibly compromised content in that case, but it could absolutely make
something worse.
Is there a use counter for how often a user demands to see an "insecure"
page? That would act as an upper limit, and maybe it's already sm
Deprecation trials require changes to servers which an enterprise may not
have access to or ability to affect changes to, whereas enterprise policies
are entirely within the enterprise's control. I'd recommend reaching out to
the enterprise team for their perspective on usage policies and perspecti
LGTM1 for the plan to remove in 112 with reverse OT until 115.
We discussed in today's meeting whether we should also have an enterprise
policy, but landed on not requesting it. The reason is that it's quite
possible that this change only breaks Twilio and nothing else, at all.
That's because of t
*Carl*, the signs are promising for other browsers to implement all the
APIs needed to run SQLite-over-Wasm. I'm optimistic!
*Randy*, how hard would it be to implement something that read user data
from Web SQL and wrote it into a parallel table structure in SQLite? Both
of these will coexist in C
Hi Blink developers,
My CL https://chromium-review.googlesource.com/c/chromium/src/+/4226754 is
failing after following the rebaseline instructions at
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/testing/web_test_expectations.md#How-to-rebaseline
. not_site_per_process_blink_web_test
LGTM to extend for 2 more milestones, given the strong evidence (landed
spec PR, positive positions) towards shipping.
+Jason Robbins - FYI, this was missed by our tools.
On Mon, Feb 6, 2023 at 8:18 PM Mason Freed wrote:
> Hi API Owners,
>
> I'd like to extend the Popover Origin Trial for 2 ad
Thanks for asking, David.
Right, the `white-space` property spec is in the middle of refactoring for
years, so it's possible that it may have some risks. I'm still
investigating multiple options for the style code, this is still
prototyping, but I hope I can minimize the risk.
On Wed, Feb 8, 2023
Your CL adds this file:
third_party/blink/web_tests/flag-specific/disable-site-isolation-trials/http/tests/serviceworker/webexposed/global-interface-listing-service-worker-expected.txt
... which is a mistake, probably the fault of the rebaseline tool. Try
removing that from the patch.
On Wed, Fe
Any thoughts you can share about why we shouldn't go straight to I2S given
population support?
Best,
Alex
On Wed, Feb 8, 2023, 7:51 PM Yoav Weiss wrote:
> LGTM to extend for 2 more milestones, given the strong evidence (landed
> spec PR, positive positions) towards shipping.
>
> +Jason Robbins
27 matches
Mail list logo
