r this feature? In particular, the lack of
> discussion of compat and interop risks is concerning.
>
> On Thu, Oct 10, 2024 at 6:10 AM Joey Arhar wrote:
>
>> Contact emailsjar...@chromium.org
>>
>> Specificationhttps://github.com/whatwg/html/pull/10557
>>
>>
Contact emailsjar...@chromium.org
Explainerhttps://open-ui.org/components/customizableselect
Specificationhttps://github.com/whatwg/html/pull/10557
Summary
This change makes the HTML parser allow additional tags in besides
, , and . This change is in support of the
customizable feature but is
Contact emailsjar...@chromium.org
Specificationhttps://github.com/whatwg/html/pull/10557
Summary
This change makes the HTML parser allow additional tags in besides
, , and . This change is in support of the
customizable feature but is being shipped first because it can be
done separately and h
;t be too hard to catch the cause
> for the behavior change in the few sites that will be affected.
>
> On Tue, May 28, 2024 at 10:33 PM Joey Arhar wrote:
>
>> > How should I interpret the results from your investigation? That none
>> of the 8 investigated sites would be n
?
>
> /Daniel
>
> On 2024-05-22 18:03, Vladimir Levin wrote:
>
>
>
> On Tue, May 21, 2024 at 2:20 PM Joey Arhar wrote:
>
>> > Do you know what the breakage looks like
>>
>> I pushed to make sure that using the old syntax with CustomStateSet.add()
>
On Tue, May 21, 2024 at 11:09 AM Vladimir Levin wrote:
> Hey,
>
> 0.04% seems like a fairly sizable number. Do you know what the breakage
> looks like or whether this usage is limited to a library/a small set of
> large websites or something else?
>
> Ideally, this
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://github.com/whatwg/html/pull/8467
Summary
The CSS custom state pseudo-class is being renamed from :--foo to
:state(foo). The new syntax, :state(foo), has been enabled by default, and
now we have to deprecate and remove the :--f
>
> Can you help me get those things clear?
>
>
>
> Mike Taylor schrieb am Dienstag, 2. Januar 2024 um 16:04:08 UTC+1:
>
>> If you don't mind - that way it will show up in our review queue.
>> On 12/28/23 4:01 PM, Joey Arhar wrote:
>>
>> > The pl
>>
>> On Wednesday, February 14, 2024 at 10:23:01 PM UTC Vladimir Levin wrote:
>>
>>> On Wed, Feb 14, 2024 at 1:53 PM Jeffrey Yasskin
>>> wrote:
>>>
>>>> Non-API-owner opinions inline:
>>>>
>>>> On Wed, Feb 14,
with
shipping now.
On Wed, Feb 14, 2024 at 1:11 PM Joey Arhar wrote:
> Contact emailsjar...@chromium.org
>
> ExplainerNone
>
> Specificationhttps://html.spec.whatwg.org/C/#unsafe-html-parsing-methods
> https://github.com/whatwg/html/pull/9538
>
> Summary
>
> The set
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://html.spec.whatwg.org/C/#unsafe-html-parsing-methods
https://github.com/whatwg/html/pull/9538
Summary
The setHTMLUnsafe and parseHTMLUnsafe methods allow Declarative ShadowDOM
to be used from javascript. In the future, they may
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/selectors-4/#open-state
https://github.com/whatwg/html/pull/10126
Summary
The :open and :closed pseudo-classes match builtin HTML elements which have
an open or closed state, including , , and .
Blink compon
Contact emailsjar...@chromium.org
ExplainerNone
Specification
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-state-pseudo-class
Summary
This is the new syntax for the CSS custom state feature for custom
elements. The old syntax, :--foo, is being deprecated and removed. This
w entry for shipping the new syntax?
>
> On Wed, Dec 27, 2023 at 3:54 AM Chris Harrelson
> wrote:
>
>> LGTM1 to ship.
>>
>> On Tue, Dec 26, 2023, 10:10 AM Joey Arhar wrote:
>>
>>> Thanks Luke!
>>> Now that WebKit is shipping, can I get approval
decision to not ship until at least another browser does the
>>>> same.
>>>>
>>>> The suggestion to avoid further massaging of the spec until another
>>>> browser has caught up was a suggestion, and not a MUST, and was not
>>>> intende
:01 AM Philip Jägenstedt
wrote:
> Hi again Joey,
>
> Can you bump this thread when you'd like to ship it?
>
> Best regards,
> Philip
>
> On Fri, Oct 6, 2023 at 7:38 PM Joey Arhar wrote:
>
>> > On the level of interest, there was no reaction on
>> ht
, it
>>>>>>> was done in order to gain consensus; in particular, the CSSWG resolution
>>>>>>> notes indicate
>>>>>>> <https://github.com/w3c/csswg-drafts/issues/4805#issuecomment-1663111980>
>>>>>>> (see
&
communication that makes you relatively sure the interest is there?
>
> On Fri, Oct 6, 2023 at 3:34 AM Joey Arhar wrote:
>
>> Contact emailsjar...@chromium.org
>>
>> Explainerhttps://github.com/whatwg/html/issues/9046
>>
>> Specificationhttps://github.com/whatwg
Contact emailsjar...@chromium.org
Explainerhttps://github.com/whatwg/html/issues/9046
Specificationhttps://github.com/whatwg/html/pull/9775
Summary
The toggle events for the popover attribute and the details element, as
well as the close event for dialog elements, currently post a task to the
D
M Alex Russell
> wrote:
>
>> hrm, this is another instance of bikeshedding after shipping, and I'm not
>> inclined to approve. Perhaps we can discuss at next week's API OWNERs
>> meeting?
>>
>> Adding others who I know are interested in this topic.
&g
nstance of bikeshedding after shipping, and I'm not
> inclined to approve. Perhaps we can discuss at next week's API OWNERs
> meeting?
>
>
> We should definitely discuss this broader subject!
>
>
>
> Adding others who I know are interested in this topic.
>
>
might have not made it clear in the spec discussions yet
that we have already shipped :--foo by default for several years.
On Fri, Sep 29, 2023 at 9:15 AM Joey Arhar wrote:
> Contact emailsjar...@chromium.org
>
> ExplainerNone
>
> Specificationhttps://github.com/whatwg/html/pull/846
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://github.com/whatwg/html/pull/8467
Summary
CSS custom state, which allows custom elements to expose their own
pseudo-classes, was shipped here:
https://groups.google.com/a/chromium.org/g/blink-dev/c/dJibhmzE73o/m/VT-NceIhAAAJ
T
select with :
https://getbootstrap.com/docs/4.0/components/dropdowns/
This intent adds support for dividers but not styling.
On Wed, Sep 20, 2023 at 8:10 AM Joey Arhar wrote:
> > Can we file a Mozilla position? (to raise awareness on their end if
> nothing else)
>
> https://github.com/moz
ed out to devrel about this
On Wed, Sep 20, 2023 at 7:54 AM Yoav Weiss wrote:
> LGTM1
>
> On Tue, Sep 19, 2023 at 7:51 PM Joey Arhar wrote:
>
>> Contact emailsjar...@chromium.org
>>
>> ExplainerNone
>>
>> Specificationhttps://github.com/whatwg/html/
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://github.com/whatwg/html/pull/9124
Summary
This feature makes the HTML parser allow tags inside tags.
These elements create horizontal borders in between elements
in the listbox popup, which we already support if you manuall
ally trigger while working
> in the debugger.
>
> /Daniel
> On 2023-08-26 19:30, PhistucK wrote:
>
> I guess all of them would be good. Not really why only a few
> pseudo-classes are listed there...
>
> ☆*PhistucK*
>
>
> On Sat, Aug 26, 2023 at 6:18 PM Joey Arhar wrote
erable?
> On 8/28/23 11:54 AM, PhistucK wrote:
>
> Thank you!
>
> ☆*PhistucK*
>
>
> On Mon, Aug 28, 2023 at 4:46 PM Joey Arhar wrote:
>
>> I filed a bug here:
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1476503
>>
>> On Sat, Aug 26,
ature request for devtools in general. I
>> wonder if we could separate it out from shipping this one set of 2 pseudo
>> classes though?
>>
>>
>>
>>
>> ☆*PhistucK*
>>
>>
>> On Sat, Aug 26, 2023 at 6:18 PM Joey Arhar wrote:
>>
>>
[image: image.png]
>
>
>
> ☆*PhistucK*
>
>
> On Sat, Aug 26, 2023 at 9:14 AM Joey Arhar wrote:
>
>> Contact emailsjar...@chromium.org
>>
>> ExplainerNone
>>
>> Specificationhttps://drafts.csswg.org/selectors-4/#user-pseudos
>>
>>
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/selectors-4/#user-pseudos
Summary
The :user-invalid and the :user-valid pseudo-classes represent an element
with incorrect or correct input, respectively, but only after the user has
significantly interacted w
Contact emailsjar...@chromium.org
ExplainerNone
Specification
https://html.spec.whatwg.org/multipage/grouping-content.html#the-search-element
Summary
The element applies a "search" role for accessibility. It is
basically the same as . From the HTML spec: The search
element represents a part of
w and enterprise
>> guards. But that obviously has a cost, so up to you if it's better to just
>> specify the current quirky behavior. Maybe our efforts are better spent
>> trying to actively drive down quirks mode usage somehow?
>>
>> Thanks for trying to clean
nks for the heads up.
>
> Mind sharing some links to the compat issues?
> On 7/27/23 8:57 PM, Joey Arhar wrote:
>
> FYI: due to compat issues I encountered while launching this feature, we
> decided to create a CSS property to opt-in to the new behavior. It was
> resolved by
give this another week to see if
>>> anyone has any feedback. But otherwise we're excited to see this ship.
>>>
>>> Rick
>>>
>>> On Wed, Mar 15, 2023 at 6:10 PM Joey Arhar wrote:
>>>
>>>> TAG review: https://github.com/w3ctag/d
a good faith effort to reach
> consensus has been made but we're at an impasse and should ship despite the
> disagreements.
>
> Thanks,
>Rick
>
> On Mon, Apr 17, 2023 at 7:12 PM Joey Arhar wrote:
>
>> Contact emailsfuth...@chromium.org, mas...@chromium.org,
Contact emailsfuth...@chromium.org, mas...@chromium.org, jar...@chromium.org
Explainer
https://github.com/chrishtr/rendering/blob/master/entry-exit-animations.md
Specificationhttps://drafts.csswg.org/css-position-4/#overlay
Summary
Introduce a overlay property to allow authors to keep elements
ike its higher than this threshold :(
On Wed, Apr 12, 2023 at 3:53 AM Yoav Weiss wrote:
> Friendly ping! :)
>
> On Wednesday, March 15, 2023 at 7:13:25 PM UTC+1 Joey Arhar wrote:
>
>> Yes, that matches my understanding. I can see on omahaproxy that the
>> usecounter was mer
r's decided, even after we ship? Or would that
> trigger breakage?
>
> On Wed, Apr 5, 2023 at 6:09 PM Joey Arhar wrote:
>
>> > Thoughts on Emilio's question on
>> https://github.com/mozilla/standards-positions/issues/762#issuecomment-1483059117
>> RE spec text
> Thoughts on Emilio's question on
https://github.com/mozilla/standards-positions/issues/762#issuecomment-1483059117
RE spec text and avoiding circularity?
This is about deciding how to implement the behavior when display:none is
specified in a keyframes rule in a way which makes it hard or imposs
on, Mar 20, 2023 at 2:03 AM Yoav Weiss wrote:
>
>
> On Wed, Mar 15, 2023 at 11:09 PM Joey Arhar wrote:
>
>> TAG review: https://github.com/w3ctag/design-reviews/issues/824
>> WebKit standards position:
>> https://github.com/WebKit/standards-positions/issues/147
>&g
TAG review: https://github.com/w3ctag/design-reviews/issues/825
WebKit standards position:
https://github.com/WebKit/standards-positions/issues/148
Mozilla standards position:
https://github.com/mozilla/standards-positions/issues/763
On Wed, Mar 15, 2023 at 1:30 PM Joey Arhar wrote:
> Cont
TAG review: https://github.com/w3ctag/design-reviews/issues/824
WebKit standards position:
https://github.com/WebKit/standards-positions/issues/147
Mozilla standards position:
https://github.com/mozilla/standards-positions/issues/762
On Wed, Mar 15, 2023 at 1:37 PM Joey Arhar wrote:
> Cont
Contact emailsfla...@chromium.org, jar...@chromium.org
Explainer
https://github.com/w3c/csswg-drafts/issues/6429#issuecomment-1318933547
Specificationhttps://drafts.csswg.org/css-display-4/#display-animation
Summary
Support specifying display and content-visibility in animations. This
support a
Contact emailsfla...@chromium.org, jar...@chromium.org
Explainer
https://github.com/w3c/csswg-drafts/issues/4441#issuecomment-1329749962
Specificationhttps://github.com/w3c/csswg-drafts/pull/8520
Summary
Allows transitions of discrete properties to be started on properties
explicitly listed in
; On Thu, Jan 26, 2023 at 5:07 PM Simon Pieters
>> wrote:
>>
>>> Hi folks!
>>>
>>> Thanks for working on this, Joey. Removing quirks where possible is
>>> always nice!
>>>
>>> On Wed, Jan 25, 2023 at 7:18 PM Joey Arhar wrote:
>>
rs would cause the spec change to land as slightly different, right?
Yes. If the WebKit signal changes things then I'll just update the behavior.
On Wed, Jan 25, 2023 at 3:15 AM Yoav Weiss wrote:
> LGTM2 for the reasons Rick pointed out.
> On Wednesday, January 25, 2023 at 6:42:39
culation. I
> think ignoring cases where the child text is empty is also fine as it'll
> avoid false positives with script updated DOM that Simon described and
> because replacing empty with non-empty string is almost certainly an
> improvement. WDYT?
>
> Rick
>
>
> On Thu
>> quite low, and ease of adaptability seems high. Also it seems clear there
>> will be a significant net accessibility benefit to this change. Thanks for
>> adding the finch kill-switch just in case we're wrong about all this.
>>
>> LGTM1
>>
>>
shipped this
behavior: https://github.com/whatwg/html/issues/2988#issuecomment-1378794167
On Thu, Jan 19, 2023 at 12:18 PM Mike Taylor wrote:
> On 1/19/23 12:54 PM, Joey Arhar wrote:
>
> Contact emails jar...@chromium.org
>
> Specification https://github.com/whatwg/html/issues
Contact emailsjar...@chromium.org
Specificationhttps://github.com/whatwg/html/issues/2988
Summary
Option elements support a "label" attribute which will cause the option to
render with the text inside the attribute rather than the child text of the
option element itself. This functionality is di
Contact emailsjar...@chromium.org
Specificationhttps://github.com/whatwg/html/pull/8199
Summary
Some changes are being made to which element is selected to get focus when
a dialog element is opened: 1. Make the dialog focusing steps look at
keyboard focusable elements instead of any focusable el
at the
>> time due to changing priorities of projects. I am happy that Joey has
>> spearheaded this work and do support this intent.
>>
>> dave.
>>
>> On Mon, Oct 17, 2022 at 8:33 AM Yoav Weiss
>> wrote:
>>
>>>
>>>
>>> On Sun, O
Contact emailsjar...@chromium.org
Specificationhttps://github.com/whatwg/html/issues/2368
https://github.com/whatwg/html/issues/5886
No changes have been made to the spec yet, but if this launch goes well
then we will likely change the HTML spec to reflect this behavior.
Summary
This will make m
2, Manuel Rego wrote:
>>>
>>> LGTM1
>>>
>>> I see this was re-discussed past week on the CSSWG and the resolution
>>> was still to keep just 1 color for this property.
>>> It's nice that you're willing to tweak the color flipping threshol
The CSSWG has resolved to rename the method to checkVisibility:
https://github.com/w3c/csswg-drafts/issues/7317
On Wed, Jun 8, 2022 at 8:36 AM Philip Jägenstedt
wrote:
> https://github.com/w3c/csswg-drafts/issues/7317 is still ongoing, so I
> think we should just wait until it's settled in the n
850#issuecomment-1010363945>.
>
> dave.
>
> On Thu, May 19, 2022 at 6:52 PM Mike Taylor
> wrote:
>
>> Given the CSSWG resolution in
>> https://github.com/w3c/csswg-drafts/issues/7274#issuecomment-1130214343,
>> LGTM1 to ship assuming we're not shipping `
> Can you ask for signals?
https://github.com/mozilla/standards-positions/issues/634
https://lists.webkit.org/pipermail/webkit-dev/2022-May/032218.html
On Wed, May 4, 2022 at 3:02 AM Yoav Weiss wrote:
>
>
> On Wednesday, May 4, 2022 at 1:08:11 AM UTC+2 Joey Arhar wrote:
>
>&
> Can you open a Mozilla position to let them know this is shipping in
Chromium?
Done: https://github.com/mozilla/standards-positions/issues/633
On Wed, May 4, 2022 at 6:04 AM mkwst via Chromestatus <
admin+mk...@cr-status.appspotmail.com> wrote:
> LGTM3.
>
> --
> You received this message beca
Contact emailsjar...@chromium.org
Explainer
https://github.com/WICG/display-locking/blob/main/explainers/isvisible.md
Specificationhttps://drafts.csswg.org/cssom-view/#dom-element-isvisible
Summary
Element.isVisible() returns true if the element is visible, and false if it
is not. It checks a v
Contact emailsjar...@chromium.org
ExplainerNone
Specificationhttps://html.spec.whatwg.org/multipage/forms.html#attr-form-rel
Summary
This feature adds the "rel" attribute to form elements, which makes it
possible to prevent window.opener from being present on websites navigated
to by form eleme
Contact emailsjar...@chromium.org
Explainer
https://github.com/WICG/display-locking/blob/main/explainers/isvisible.md
Specificationhttps://drafts.csswg.org/cssom-view/#dom-element-isvisible
Summary
Element.isVisible() returns true if the element is visible, and false if it
is not. It checks a v
Contact emailsjar...@chromium.org
Explainer
https://github.com/WICG/display-locking/blob/master/explainers/hidden-content-explainer.md
Specificationhttps://github.com/whatwg/html/pull/7475
Design docs
https://github.com/WICG/display-locking/blob/master/explainers/hidden-content-explainer.md
Sum
ave any update on the ongoing "Autofill in ShadowDOM" issue, is
> there a solution in place, if not then when can we expect the release/live?
>
> Thanks in Advance,
> Prerana
>
> On Tuesday, February 22, 2022 at 10:42:28 PM UTC+5:30 Joey Arhar wrote:
>
>> > Do
> Does this works in other browsers? Have we reported bugs if it doesn't?
I just found this WebKit bug someone else reported:
https://bugs.webkit.org/show_bug.cgi?id=172567
I'm guessing this means it doesn't work in WebKit, at least.
On Thu, Feb 17, 2022 at 12:21 PM Joey Arha
new HTML features — which would
> likely work out-of-the-box anyhow. Please follow this guide and elaborate
> on how developers would inspect & debug this new feature please. Thanks!
>
> On Wednesday, February 16, 2022 at 7:30:31 PM UTC+1 Joey Arhar wrote:
>
>> > Yea
> Yeah, and there's already an issue about that:
> https://github.com/web-platform-tests/wpt/issues/27118
Thanks! I'll watch this in case I can ever add WPTs for this.
> Does this works in other browsers? Have we reported bugs if it doesn't?
I don't think other browsers do this, but I couldn't g
e.
>
> -mike
>
>
> On Fri, Oct 1, 2021 at 11:42 AM Balazs Engedy wrote:
>
>> Thank you for the detailed differential threat analysis, SGTM from the
>> permissions side. Glad to see the ongoing work on robust and comprehensive
>> mitigations.
>>
>>
> in anticipation of a future world where the preexisting vectors of
snooping have been mitigated
I am planning on adding a delay to find-in-page in order to mitigate
find-in-page snooping which would work with this feature, beforematch, and
the existing scroll events:
https://bugs.chromium.org/p/
(in a quiz type of thing) via this element...
>
> ☆*PhistucK*
>
>
> On Sat, Sep 18, 2021 at 6:55 PM Joey Arhar wrote:
>
>> > Will there be an opt out (without resorting to using other elements)?
>>
>> No, there is no plan to add an opt-out for this featu
On Fri, Sep 17, 2021 at 4:55 PM Joey Arhar wrote:
>
>> > I think it's fair to say "positive", given the like and retweet signals
>> on https://twitter.com/tomayac/status/1403119516922662913 and
>> https://twitter.com/tomayac/status/1293696281370669057 where th
assuming correctly that developer opt-in is not required.
On Fri, Sep 17, 2021 at 1:56 AM Yoav Weiss wrote:
>
>
> On Fri, Sep 17, 2021 at 8:41 AM 'Thomas Steiner' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>>
>>
>> On Fri, Sep 17, 2021 at 3:
Contact emailsjar...@chromium.org
Explainer
https://github.com/WICG/display-locking/blob/main/explainers/auto-expanding-details-explainer.md
Specificationhttps://github.com/whatwg/html/pull/6466
Design docs
https://github.com/WICG/display-locking/blob/main/privacy-assessments/auto-expanding-deta
73 matches
Mail list logo
