Re: [webkit-dev] When should I use AtomicString vs String?

Are there any advantages to String over AtomicString? On Fri, May 31, 2013 at 11:14 PM, Daker Pinheiro daker.pinhe...@openbossa.org wrote: It is faster to compare and hash AtomicString than regular Strings. On Fri, May 31, 2013 at 5:57 PM, Brendan Long s...@brendanlong.comwrote: I hope

[webkit-dev] The SrcN responsive images proposal

Hello WebKiteers, I'd like to get the project's opinion on a recent responsive image proposal by Tab Atkins dubbed srcN: http://tabatkins.github.io/specs/respimg/Overview.html This proposal covers all the major responsive images use-cases: DPR based resource selection, viewport dimensions based

Re: [webkit-dev] The SrcN responsive images proposal

On Oct 20, 2013 11:31 AM, PERIER Romain romain.per...@gmail.com wrote: Hi all, srcset is not complicated enough for a web developer? why do you want to add complexity for the developer ? The srcset specification already convers DRP switching and viewport The reasoning behind the new proposal

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa rn...@webkit.org wrote: On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: On Sun, Oct 20, 2013 at 10:07 AM, Antti Koivisto koivi...@iki.fi wrote: Ignoring other aspects of this, the idea of making attribute name an

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Oct 24, 2013 at 7:06 PM, Maciej Stachowiak m...@apple.com wrote: On Oct 23, 2013, at 11:24 PM, Yoav Weiss y...@yoav.ws wrote: On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa rn...@webkit.org wrote: On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: On Sun

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Oct 24, 2013 at 9:33 AM, Ryosuke Niwa rn...@webkit.org wrote: On Wed, Oct 23, 2013 at 11:24 PM, Yoav Weiss y...@yoav.ws wrote: On Wed, Oct 23, 2013 at 10:22 PM, Ryosuke Niwa rn...@webkit.org wrote: On Tue, Oct 22, 2013 at 1:50 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: On Sun

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Nov 6, 2013 at 9:00 PM, Maciej Stachowiak m...@apple.com wrote: (b) I am dubious of some of the use cases proposed as essential for src-N that ratchet up the complexity. For example, your case #2 of viewport-switching Viewport switching is very common in almost any responsive

Re: [webkit-dev] The SrcN responsive images proposal

On Wed, Nov 6, 2013 at 11:33 PM, Benjamin Poulain benja...@webkit.orgwrote: On 11/6/13, 10:53 AM, John Mellor wrote: On Sun, Oct 20, 2013 at 2:00 AM, Maciej Stachowiak m...@apple.com mailto:m...@apple.com wrote: My initial impression is that it seems a bit overengineered. I

Re: [webkit-dev] The SrcN responsive images proposal

On Thu, Nov 7, 2013 at 3:32 AM, Benjamin Poulain benja...@webkit.orgwrote: On 11/6/13, 3:24 PM, Yoav Weiss wrote: On Wed, Nov 6, 2013 at 11:33 PM, Benjamin Poulain benja...@webkit.org mailto:benja...@webkit.org wrote: On 11/6/13, 10:53 AM, John Mellor wrote: On Sun, Oct 20

Re: [webkit-dev] The SrcN responsive images proposal

I think this discussion might be more fruitful at a vendor neutral forum, so I've started a thread out on the WHATWG: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-November/041369.html On Fri, Nov 8, 2013 at 6:06 PM, John Mellor joh...@chromium.org wrote: Most discussion so far

Re: [webkit-dev] The SrcN responsive images proposal

On Fri, Nov 8, 2013 at 8:44 PM, Maciej Stachowiak m...@apple.com wrote: On Nov 7, 2013, at 2:38 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Thu, Nov 7, 2013 at 9:24 AM, Timothy Hatcher timo...@apple.com wrote: As I replied before, there should only be one attribute — srcset. I

[webkit-dev] Picture element implementation

Hi all, I'm currently implementing the picture elementhttp://picture.responsiveimages.org/ in Blink, to extend the srcset implementation and handle more responsive images use-caseshttps://groups.google.com/a/chromium.org/d/msg/blink-dev/vuLeAM9fJww/UHnMz7QLRWgJ . I'd be interested in working

Re: [webkit-dev] Picture element implementation

On Mon, Mar 31, 2014 at 10:59 PM, Benjamin Poulain benja...@webkit.org wrote: On 3/31/14, 9:32 AM, Yoav Weiss wrote: I'm currently implementing the picture element http://picture.responsiveimages.org/ in Blink, to extend the srcset implementation and handle more responsive images use-cases

Re: [webkit-dev] Picture element implementation

I've landed support for the sizes part of the syntax, currently on HTMLImageElement only, behind an off-by-default compile time flag. What is the proper procedure to request permission to turn on the flag by default? On Sun, Jun 15, 2014 at 11:31 PM, Yoav Weiss y...@yoav.ws wrote: On Mon, Mar

Re: [webkit-dev] Picture element implementation

On Tue, Jul 1, 2014 at 11:53 PM, Maciej Stachowiak m...@apple.com wrote: In fairness I should note that enabling by default in nightlies doesn’t necessarily mean anyone will ship it right away. But it’s still a good thing to do to get better test coverage. I fully understand it doesn't mean

Re: [webkit-dev] Client Hints

+Ilya for spec related questions. Also, I forgot to mention it, but my intention is to implement the RW and DPR hints first, and see about the MD and RQ hints (which are newer to the spec) later on. On Thu, Apr 23, 2015 at 7:02 PM, Maciej Stachowiak m...@apple.com wrote: Additional spec

[webkit-dev] Client Hints

Hi, As I've discussed during my session at the contributor's meetup, I'm interested in implementing Client-Hints http://igrigorik.github.io/http-client-hints/ in WebKit. For those unfamiliar with it, Client-Hints is a standard destined to improve content negotiation, and enable the browser to

Re: [webkit-dev] Client Hints

(Re) Posting Ilya's response from April 24th, since his response wasn't published on the mailing list archive for some reason. On Thu, Apr 23, 2015 at 1:37 PM, Yoav Weiss y...@yoav.ws wrote: +Ilya for spec related questions. Also, I forgot to mention it, but my intention is to implement

Re: [webkit-dev] Client Hints

And (Re) Posting Mark's response from April 25th, for the same reasons. On 24 Apr 2015, at 2:32 pm, Ilya Grigorik i...@igvita.com wrote: On Thu, Apr 23, 2015 at 7:02 PM, Maciej Stachowiak m...@apple.com wrote: Is the Internet-Draft for this planned to become a standards-track RFC? Is there an

Re: [webkit-dev] Client Hints

on this proposal? - Maciej On Apr 28, 2015, at 8:42 AM, Yoav Weiss y...@yoav.ws wrote: (Re) Posting Ilya's response from April 24th, since his response wasn't published on the mailing list archive for some reason. On Thu, Apr 23, 2015 at 1:37 PM, Yoav Weiss y...@yoav.ws wrote: +Ilya

Re: [webkit-dev] Client Hints

On Wed, May 6, 2015 at 8:41 AM, Ryosuke Niwa rn...@webkit.org wrote: On Tue, May 5, 2015 at 11:35 PM, Yoav Weiss y...@yoav.ws wrote: On Wed, May 6, 2015 at 8:14 AM, Ryosuke Niwa rn...@webkit.org wrote: I do have the same concern over terse names. I don't see any point in saving 13 bytes

[webkit-dev] Removing the srcset/sizes flag

Hi, Currently the srcset `w` descriptor and the `sizes` attribute implementation is behind an on-by-default flag. After a twitter exchange https://twitter.com/awfulben/status/595852748375068672 with Ben, I've added a bunch https://bugs.webkit.org/show_bug.cgi?id=144766 of tests

Re: [webkit-dev] Client Hints

On Wed, May 6, 2015 at 9:09 PM, Maciej Stachowiak m...@apple.com wrote: Some more questions/comments about RW: - Is maybe-image-width-maybe-viewport-width a useful value? Perhaps there should be an always-present header for viewport width, and one for resource width that is present only

Re: [webkit-dev] Removing the srcset/sizes flag

Build flag was removed. Thanks all! On Fri, May 8, 2015 at 10:51 AM, Yoav Weiss y...@yoav.ws wrote: Hi, Currently the srcset `w` descriptor and the `sizes` attribute implementation is behind an on-by-default flag. After a twitter exchange https://twitter.com/awfulben/status

Re: [webkit-dev] Content-DPR header

On Sun, May 31, 2015 at 4:54 AM, Sam Weinig wei...@apple.com wrote: Hi Yoav, Sorry, but I’m afraid I’m still not really getting it. Can you get even more concrete? Perhaps provide some a sample page that would need this kind of functionality and go through what Content-DPR values would be

Re: [webkit-dev] Content-DPR header

On Sat, May 30, 2015 at 12:32 AM, Simon Fraser simon.fra...@apple.com wrote: As others have said, doing this at the transport layer seems wrong. HTTP is an application layer protocol, and is already used to convey all kinds of data about the payload that it delivers, such as content-type,

Re: [webkit-dev] Content-DPR header

exercise applies, but would require the full-fledged Client-Hints in order to actually deliver resized images. On May 29, 2015, at 11:23 AM, Yoav Weiss y...@yoav.ws wrote: As a first step towards the Client-Hints implementation, I submitted a patch https://bugs.webkit.org/show_bug.cgi?id=145380

[webkit-dev]

Hi, I'm interested in adding support for and the corresponding "Link:" headers and wanted to gauge interest for supporting the feature. The preload relationship provides a declarative fetch primitive that enables developers to initiate a resource fetch and

Re: [webkit-dev]

Hello Alexey, On Wed, Nov 18, 2015 at 1:27 AM, Alexey Proskuryakov wrote: > Hello Yoav, > > Is there any technology on the horizon that would simplify doing this kind > of optimization? If done manually, this seems: > - complicated, so only a few sites will do this; > - very

Re: [webkit-dev]

Apologies for the long silence on this subject. A patch for initial support of the feature is at https://bugs.webkit.org/show_bug.cgi?id=156334. ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Using ResourceTiming API for testing

Hey, As part of implementing support for `` more tests are needed to make sure resources are properly reused. The easiest way to test that is using the ResourceTiming API, which is currently implemented behind an off-by-default build-time flag. Therefore, I'd like to move the implementation of

[webkit-dev] Reseting runtime-flag enabled features and IndexedDB

After encountering flakiness as a result of runtime flags leaking between tests, I wrote a patch that resets all feature flags to their default values between tests. The problem I encountered was that IndexedDB was turned off by default in

Re: [webkit-dev] CSS Parse error in element.

Hi Atul, I second Alex's suggestion (perhaps followed by HTMLLinkElement::process() and other places in that file that refer to `hrefAttr`). If you have a test case online, I could try to take a look and maybe provide more guidance. Cheers :) Yoav On Fri, Feb 3, 2017 at 9:19 PM Alex Christensen

[webkit-dev] Importing tests from web-platform-tests

I'm trying to import tests from web-platform-tests/preload , but having trouble getting them to run without requiring expected results and while using wptserve. I looked at the WPT import tutorial

[webkit-dev] "ReflectOnly" IDL equivalent

I'm working on the link preload feature and as part of that want to align it to the spec from an IDL perspective. The `as` attribute is defined as an "enumerated attribute", which reflects only a finite set of known values. That is important for feature

Re: [webkit-dev] "ReflectOnly" IDL equivalent

Apologies for not updating this thread sooner. I already went ahead and implemented `as()` to reflect what's needed, and was planning to refactor that and add a "ReflectEnum" binding at a later patch. If that's not needed, I can just leave it as is.

Re: [webkit-dev] Proposal for an "intent to" process for web-exposed features

On Thu, Feb 27, 2020 at 6:24 PM Maciej Stachowiak wrote: > > I think we should have some structure, not just freeform emails. We can > start with a simple template, but there’s some info that folks almost > always want, so it’s easier if it’s included in the first place, rather > than needing

Re: [webkit-dev] WebKit position on Paint Timing / (first paint, first contentful paint)

On Thu, Feb 27, 2020 at 11:47 AM Noam Rosenthal wrote: > > > On Thu, Feb 27, 2020 at 12:17 PM Yoav Weiss wrote: > >> >> >> On Wed, Feb 26, 2020 at 11:33 PM Ryosuke Niwa wrote: >> >>> >>> I don't think we should do that. For starters, C

Re: [webkit-dev] WebKit position on Paint Timing / (first paint, first contentful paint)

On Wed, Feb 26, 2020 at 11:33 PM Ryosuke Niwa wrote: > > On Wed, Feb 26, 2020 at 10:54 AM Noam Rosenthal wrote: > >> (resending from correct address) >> On Wed, Feb 26, 2020 at 8:08 PM Maciej Stachowiak wrote: >> >>> >>> Some quick comments: >>> >> >>> the definition of First Contentful Paint

[webkit-dev] Developer tools when running Safari with a local WebKit build

Hey! I'm trying to run a webkit build using the `run-safari` script, and I cannot seem to be able to set the Preferences to enable developer tools (unlike when running regular Safari). Is there a way to enable it that I'm missing? Thanks! :) Yoav ___

[webkit-dev] Position on User-Agent Client Hints

Hey WebKit folks, I'd like to ask for your official position on the User Agent Client Hints specification. +Maciej Stachowiak has been providing great feedback on the proposal, as well as to the underlying Client Hints Infrastructure

Re: [webkit-dev] Position on User-Agent Client Hints

On Fri, May 8, 2020 at 6:01 PM Alex Christensen wrote: > Last I recall talking about this, we did not oppose to client hits header > fields in general, just some specific ones that expose information we do > not wish to expose to reduce fingerprinting information. For example, I > think we do

Re: [webkit-dev] User Agent Client Hints

Friendly ping! :) On Wed, Sep 30, 2020 at 9:29 AM Yoav Weiss wrote: > Hi WebKit folks, > > Circling back on the previous discussion > <https://lists.webkit.org/pipermail/webkit-dev/2020-May/031195.html> > about User-Agent ClientHint. The feature was implemented in Chromium

Re: [webkit-dev] Request for position on Event Timing

+Nicolás Peña On Sun, Aug 9, 2020 at 5:40 AM Ryosuke Niwa wrote: > On Fri, Aug 7, 2020 at 2:09 PM Rob Buis wrote: > > > > I was not aware of Long Tasks API. However it seems to have a slightly > > different focus (task vs. input events). Also I am mostly interested in > > First Input Delay,

[webkit-dev] User Agent Client Hints

Hi WebKit folks, Circling back on the previous discussion about User-Agent ClientHint. The feature was implemented in Chromium and is being rolled out in Chrome. There were some concerns mentioned in the previous thread, that

Re: [webkit-dev] Suggesting to enable paint timing by default

+Ryosuke Niwa +Alex Christensen who were involved in the spec discussions. On Wed, May 27, 2020 at 10:29 AM Noam Rosenthal wrote: > > > Following up on this. > >> FOn Tue, May 12, 2020 at 10:28 AM Maciej Stachowiak >> wrote: >> >>> >>> >>> On May 11, 2020, at 9:53 PM, Noam Rosenthal wrote:

Re: [webkit-dev] User Agent Client Hints

Yet-another ping! :) On Wed, Oct 7, 2020 at 8:23 AM Yoav Weiss wrote: > Friendly ping! :) > > On Wed, Sep 30, 2020 at 9:29 AM Yoav Weiss wrote: > >> Hi WebKit folks, >> >> Circling back on the previous discussion >> <https://lists.webkit.org/pipermail/we

Re: [webkit-dev] User Agent Client Hints

Thanks for the background. Let's continue to discuss on the issue. On Tue, Nov 3, 2020 at 12:32 AM Maciej Stachowiak wrote: > > > On Nov 2, 2020, at 8:56 AM, Yoav Weiss wrote: > > Thanks for re-reviewing, Maciej! > > Adding Mike Taylor, who's likely to take a closer loo

Re: [webkit-dev] User Agent Client Hints

it doesn't outlive current same-origin client-side storage. Am I understanding the Client Hints Infrastructure correctly? > > On Nov 2, 2020, at 3:32 PM, Maciej Stachowiak wrote: > > > > On Nov 2, 2020, at 8:56 AM, Yoav Weiss wrote: > > Thanks for re-reviewing, Mac

Re: [webkit-dev] User Agent Client Hints

/github.com/WICG/ua-client-hints/issues/37#issuecomment-576730548> adding a Feature Policy (now Permission Policy) to that effect. Would that help with your concerns? > (perhaps even expanding beyond what is currently possible with the UA > string). > Can you expand on that last poin

[webkit-dev] Request for position: Aligning high-resolution timer granularity to cross-origin isolated capability

Hey folks, We recently changed the HR-time spec to better align its resolution clamping with cross-origin isolated capability

Re: [webkit-dev] Request for position: Aligning high-resolution timer granularity to cross-origin isolated capability

-Spectre timing attacks? > Could you elaborate on those 2 points? > > Thanks, > Geoff > > On Mar 17, 2021, at 3:38 AM, Yoav Weiss via webkit-dev < > webkit-dev@lists.webkit.org> wrote: > > Hey folks, > > We recently changed <https://github.com/w3c/hr-time/p

[webkit-dev] Request for position on AudioContext.outputLatency

(Sent on behalf of Hongchan Choi, who failed to subscribe to this mailing list) Hey folks! AudioContext.outputLatency is to inform the time at which the first sample in the buffer is actually processed by the audio output device. This is useful when synchronizing the audio generated by Web Audio

Re: [webkit-dev] Request for position on AudioContext.outputLatency

ng if it means this >> allows a web page to passively identify user speakers. >> Say I switch from builtin speakers to Bluetooth headset using MacOS >> system menu. >> >> If so, the spec should identify this as potential fingerprinting and >> should provide mitigations.

Re: [webkit-dev] Request for position on AudioContext.outputLatency

gt;> >>> Cheers, >>> Hongchan >>> >>> >>> On Mon, Dec 13, 2021 at 1:15 AM youenn fablet wrote: >>> >>>> Looking at >>>> https://www.w3.org/TR/webaudio/#dom-audiocontext-outputlatency, it >>>> states that: