Just curious, I saw this go by
> Blob.bytes collapses this two-step ritual into a single call, returning
a Uint8Array. By removing the extra allocation and copy, it trims
garbage-collection overhead and lowers latency when processing large blobs.
There should be no extra allocation as it is
Does this enable more detection of incognito mode by sites?
On Mon, Jul 14, 2025 at 1:08 PM 'Zainab Rizvi' via blink-dev <
blink-dev@chromium.org> wrote:
> Hi, Alex! This will only be enabled for Chrome's Incognito mode.
>
> On Mon, Jul 14, 2025 at 2:19 PM Alex Russell
> wrote:
>
>> Will this be
I have requested all the reviews. What else do I need to do to get his
approved?
[image: Screenshot 2025-06-05 at 10.26.36.png]
On Tuesday, May 27, 2025 at 11:22:16 AM UTC-7 Mike Taylor wrote:
> Could you please request privacy, security, enterprise, and debuggability
> bits in your chromestat
Sorry if I'm not up on all of the latest. I have several sites that use
blobs in iframes to implement user code execution (think JSFiddle/Codepen).
Do I need to be worried?
Some use top-level->iframe(blob-from-top-level). Others use
top-level->iframe(3rd-party)->iframe(blob-from-3rd-party)
They a
I'm just curious. Why is it a DOMString and not a boolean? I didn't see
that in the explainer
On Mon, Jul 29, 2024 at 12:00 PM Chromestatus <
ad...@cr-status.appspotmail.com> wrote:
> Contact emails adam.ettenber...@microsoft.com
>
> Explainer
> https://github.com/MicrosoftEdge/MSEdgeExplainers
The link to the specification:
https://github.com/w3c/csswg-drafts/pull/9699 list
behaviors and then says
> Web compat analysis: the above is what is already implemented in WebKit
and Chromium browsers
But one of the behaviors listed is
> devicePixelRatio is affected by zoom inherited from a
On Fri, Nov 10, 2023 at 1:31 AM Rick Byers wrote:
> On Wed, Nov 8, 2023 at 5:56 PM Gregg Tavares wrote:
>
>> Changing the event order seems like something you'd be opting into since
>> this API has not shipped yet.
>>
>> Don't use the API, get the exis
ask about getting you opted in to that rollout.
>>>
>>>
>>>
>>> For reconversions, when a page is using EditContext the same UI will
>>> still be available to the user via the menu or hotkeys. The page keeps the
>>> platform informed about which
a, e.g. this one
> <https://github.com/w3c/uievents/issues/75> from before Gecko started
> firing keydown/keyup events during composition; maybe this should be taken
> back up by the WG to try to drive further interoperability in the area. If
> we end up making a change the
Not a decider but one that sees the IME on many sites that try to roll
their own text input.
This sounds like a "if you do all of these 30 things perfectly, then maybe
your site will work with most IME issues but you won't know unless you get
someone experienced with IME users to test for you" sol
What is the point of this throttling given the workarounds (postMessage?)
or maybe postMessage is going to be throttled?
I've used this to make something that takes a long time not freeze the
browser
const wait = _ => new Promise(resolve => setTimeout(resolve));
for (many-operations) {
doOper
11 matches
Mail list logo
