Re: [blink-dev] Blink version

Chrome://version will tell you the chromium version. Blink is in the main repository and is not versioned separately. On Mon, Apr 22, 2024, 10:43 AM Alexander Low wrote: > May I know is there any information about Blink? I try to find it but I > could not manage to make it. Is there any method

Re: [blink-dev] Re: Chromium’s migration to the new issue tracker begins Feb 2

It's issue-tracker-support at chromium.org On Wed, Jan 31, 2024, 8:31 PM David Dabbs wrote: > Thank you for the reminder Joe. > My digest message does not include a full e-mail address: > >You can reach out at any time to issue-trac...@chromium.org > with

Re: [blink-dev] Intent to Prototype: Call stacks in crash reports from unresponsive web pages

shing only under the >> presence of extension-injected code in the main world, then that's critical >> information for the site owner to know from a customer support perspective. >> >> Rick >> >> On Wed, Jan 24, 2024 at 3:10 PM Dave Tapuska >> wrote: &g

Re: [blink-dev] Intent to Prototype: Call stacks in crash reports from unresponsive web pages

Just a few thoughts... I haven't seen a proposed implementation but I presume you are going to restrict this only to execution stacks in the main world? If you get an extension executing scripts in the main world how will you prevent the endpoint from knowing about the agent's execution

Re: [blink-dev] Intent to Prototype: Partitioning :visited links history

I look forward to this. Will this include an implementation whereby the visited links are only sent to the relevant AgentSchedulingGroup/SiteInstanceGroup? My recollection is that the visited link map was propagated to each renderer unconditionally. Dave On Wed, Jun 28, 2023, 3:21 AM Yoav Weiss

Re: [blink-dev] Allow Navigator.registerProtocolHandler to register "payto"

I feel the chromestatus is a bit misleading on the Mozilla position. It indicates "Worth Prototyping" with a link to the Mozilla positions github issue. But no one from Mozilla has indicated a position. dave. On Thu, Apr 13, 2023 at 3:05 PM Rastislav Vašička < rastislav.vasi...@codetech.cc>

Re: [blink-dev] Intent to Ship: Send Mouse Events to Disabled Form Controls

So the initial attempt was problematic for interop due to mouseup, and mousedown being displaced for the entire event path. I had removed my request to ship in order to address the concerns of other vendors (proposed another 3 milestones to collect more data). It appears this attempt does fix that

Re: [blink-dev] Debugging compressed pointers in Blink

Anton, can you add this to https://source.chromium.org/chromium/chromium/src/+/main:docs/linux/debugging.md ? On Tue, Oct 11, 2022 at 10:19 AM Anton Bikineev wrote: > I'm now submitting a CL > that adds > some quick gdb helpers: > >

Re: [blink-dev] Intent to Ship: Prerender2 for Desktop

extension stores, look for > patterns that would be affected by this change and notify the extension's > authors ahead of time? > > On Thu, Sep 1, 2022 at 4:23 PM Dave Tapuska wrote: > >> I drafted a blog post highlighting the additions/changes to the extension >> APIs. It

Re: [blink-dev] Intent to Ship: Prerender2 for Desktop

I drafted a blog post highlighting the additions/changes to the extension APIs. It is just going through reviews before being posted to developer.chrome.com, hopefully sometime next week. dave. On Thu, Sep 1, 2022 at 2:49 AM Yoav Weiss wrote: > > > On Thu, Sep 1, 2022 at 8:24 AM Takashi

Re: [blink-dev] Intent to Experiment: Align Timers (including DOM timers) at 125 Hz

Stefan, this was just for "non-zero delay" timers? Are there still potential issues there? On Fri, Aug 5, 2022 at 1:19 PM Stefan Zager wrote: > This is a common programming pattern: > > requestAnimationFrame(() => { > setTimeout(() => { > // At this point, it's very likely that layout is

Re: [blink-dev] Re: Intent to Ship: Element.isVisible method

t; for RemoteFrames would probably have security/privacy considerations. > > On Thu, May 19, 2022 at 5:17 PM Dave Tapuska > wrote: > >> So how does this method work for iframes that have their visibility >> hidden? Is it intended to work for that? >> >> >>

Re: [blink-dev] Re: Intent to Ship: Element.isVisible method

So how does this method work for iframes that have their visibility hidden? Is it intended to work for that? div's isVisible will always be true. Perhaps isVisible needs a caveat that it only works for the current document. Oh that is what was debated here

Re: [blink-dev] Intent to Ship: Same-origin prerendering triggered by the speculation rules API

This intent is for Android only, correct? Will there be another Intent to Ship on Desktop? Presumably desktop is blocked on extensions and the compatibility risk regarding those. (I recently discussed this at the WECG

Re: [blink-dev] Fwd: Can't run Web Tests locally on MacOS 12 device

FYI... Seems PHP was removed in macOS Monterey. Nico sounds like we need to revert your patch. dave On Thu, Dec 16, 2021 at 5:20 PM Dave Tapuska wrote: > I get it too.. I wonder if > https://source.chromium.org/chromium/chromium/src/+/1156f94e35e73182126f17cf52c45f70a8d4c45b > is

Re: [blink-dev] Fwd: Can't run Web Tests locally on MacOS 12 device

I get it too.. I wonder if https://source.chromium.org/chromium/chromium/src/+/1156f94e35e73182126f17cf52c45f70a8d4c45b is the cause because my default system http conf doesn't have a PHP library. Nico? dave. On Thu, Dec 16, 2021 at 5:01 PM 'Alexis Hétu' via blink-dev < blink-dev@chromium.org>

Re: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

ough, then please let me know! > > > > *From:* Dave Tapuska > *Sent:* Wednesday, October 27, 2021 2:27 PM > *To:* Anupam Snigdha > *Cc:* slightly...@chromium.org; blink-dev@chromium.org; > yoavwe...@chromium.org; Bo Cupp ; Scott Low < > sc...@microsoft.com>; gary

Re: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

I was looking at the implementation of this. Is it possible to move the check of the policy to be based in the browser when the map is fetched? As of right now the policy enforcement is on the renderer side, so a compromised renderer can request the keyboard map. dave. On Wed, Oct 27, 2021 at