[blink-dev] Re: Intent to Ship: Increased max nesting level for setTimeout(0)

On Fri, Oct 21, 2022 at 12:31 PM Etienne Pierre-doray wrote: > Is that a very new change? Is there a reason for us to continue to look at >> (or cite) 2.0 when 2.1 is live? >> > I think that happened in August. sky@ or +hpayer@ might be able to answer > this. > 2.1 is the new version. We can ign

[blink-dev] Re: Intent to Ship: Increased max nesting level for setTimeout(0)

> > Is that a very new change? Is there a reason for us to continue to look at > (or cite) 2.0 when 2.1 is live? > I think that happened in August. sky@ or +hpayer@ might be able to answer this. What's the residual delta now that 2.1 is available to test against? > Measured on Canary MacBook pro

Re: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

Thomas I read the web-custom-formats and this is a very nice addition but doesn't quite solve my exact problem of interop with desktop applications. Specially Microsoft, Adobe, and other desktop products copy unsanitized html to the clipboard and I need to be able to access this content via to

Re: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

Thank you and thank you again for the quick response. On Fri, Oct 21, 2022 at 1:18 PM Ana Sollano Kim wrote: > Hi, > > > > The change to introduce read/write unsanitized HTML content to/from the > clipboard is still in review, not yet merged. Please see [Clipboard API] > Write unsanitized HTML c

Re: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

Could I get clarification on the #clipboard-unsanitized-content flag? When I enable this the Async API writes unsanitized html which is great but when I call the following I don't see a new html and the original "text/html" is still sanitized. I am testing against 107 beta on 10/21/2022. I ha

Re: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

This is what is implemented in Chrome: https://developer.chrome.com/blog/web-custom-formats-for-the-async-clipboard-api/ . -- Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com, https://twitter.com/tomayac) Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany Geschäfts

RE: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

Hi, The change to introduce read/write unsanitized HTML content to/from the clipboard is still in review, not yet merged. Please see [Clipboard API] Write unsanitized HTML content to the clipboard (Ife196418) · Gerrit Code Review (googlesource.com)

Re: [blink-dev] Intent to Ship: CSS `hyphenate-limit-chars` property

> > We could probably take this as a positive signal, despite not being a > formal position - there's a WIP patch written by :jfkthame that's been > reviewed. But I asked just in case, > https://bugzilla.mozilla.org/show_bug.cgi?id=1521723#c9. Thank you. Could we request a signal via https://git

[blink-dev] Intent to Ship : HTTP response status code in Resource Timing

Contact emails abin.pa...@gmail.com Explainer https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md Specification Resource Timing PR : https://github.com/w3c/resource-timing/pull/335 Fetch PR : https://github.com/whatwg/fetch/pull/1468 HTML PR :https://githu

Re: [blink-dev] Intent to Ship: CSS `hyphenate-limit-chars` property

On 10/21/22 3:47 AM, Koji Ishii wrote: Contact emails ko...@chromium.org Explainer None Specification https://w3c.github.io/csswg-drafts/css-text-4/#propdef-hyphenate-limit-chars Summary This property specifies the m

Re: [blink-dev] Intent to Experiment: Back/forward cache NotRestoredReason API

LGTM to experiment from M108 to M110 inclusive. Out of curiosity, where did we land on extensions? https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/NotRestoredReason.md#extension-usage On 10/21/22 3:34 AM, 'Yuzu Saijo' via blink-dev wrote: Contact emails yu...@goog

Re: [blink-dev] Intent to Ship: Origin Isolation By Default / Deprecate document.domain

On Wed, Oct 19, 2022 at 5:23 AM Yoav Weiss wrote: > Thanks for the detailed report!! > > It's great that we've managed to bring the usage down, but 0.25% is still > too high for my comfort levels. > Taking a manual survey of the major users seems like the right approach. I > wonder if you could,

Re: [blink-dev] Intent to Implement and Ship: Trusted Types fromLiteral

Apologies this took a while, but the explainer bit has now landed here: https://github.com/w3c/trusted-types/blob/main/explainer.md#source-literals On Wed, Oct 19, 2022 at 5:34 PM Yoav Weiss wrote: > Friendly ping on an explainer update :) > > On Thursday, October 6, 2022 at 7:19:20 PM UTC+2 Jun

[blink-dev] Intent to Ship: CSS `hyphenate-limit-chars` property

Contact emailsko...@chromium.org ExplainerNone Specification https://w3c.github.io/csswg-drafts/css-text-4/#propdef-hyphenate-limit-chars Summary This property specifies the minimum number of characters in a hyphenated word. When applying the hyphenation, the optimal minimum number of character

[blink-dev] Intent to Experiment: Back/forward cache NotRestoredReason API

Contact emailsyu...@google.com, yu...@chromium.org, fer...@chromium.org Explainer https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/NotRestoredReason.md Design docs https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/NotRestoredReason.md Summary NotRestoredReason