03:46
<Farzaneh Sedarati>
so I used swift fiddle to transfer money from these Sha string to my bank account and I did over a hundred different string on 4 transfer code on fiddle Saturday evening and still no deposits yet
09:05
<annevk>
Noam Rosenthal: did you see the latest moveBefore() comment against the HTML PR? I think it can be dismissed, but I'd like you or Dominic Farolino to do it.
09:09
<emilio>
IIRC we moved to that model because we didn't want sync moving of focus. Chrome used to do sync moving of focus but no other browser did.
Chrome used to do sync moving in some cases, and async in others (off a timer) fwiw :)
09:11
<emilio>
key events may come in between something becoming inert and rendering steps
Yes, but rendering generally changes focusability as well (via display / visibility / etc), so seems nicer just doing the fixup once than doing it sync on DOM changes and async on style changes (specially since you'd need to do a style update when e.g. you add or remove the inert / tabindex / etc attributes)
09:12
<emilio>
I guess only in some cases, but still
10:38
<Noam Rosenthal>
I'll take a look, thanks!
11:45
<annevk>
Noam Rosenthal: it also seems there's one comment still open on filing a follow-up issue and one formatting concern. I might have time later today, but maybe it's best to merge it all next week at this point.
13:03
<Noam Rosenthal>
I responded to the former, will defer to Dominic Farolino for the formatting thing.
13:26
<Luke Warlow>
ntim: should there be a pseudo-element for <input type=color>? If we add eyedropper to it, we'd want a different icon in the button and allow customization
Fyi I've added a ::color-swatch pseudo element to that draft. All the browsers have one so we should implement it for base. Makes the implementation in browsers less magic too.
13:36
<annevk>
Luke Warlow: if you want macOS-style appearance I think you need an additional (child) box, assuming you care about <input type=color alpha>. It's possible it all could be achieved through ::before and ::after though. Also not entirely sure I would count this yet as removing magic, maybe a tiny bit.
13:37
<annevk>
And it might not actually remove magic if we decide that appearance: auto has to be behave as a replaced element without addressable inner parts.
13:37
<Luke Warlow>
I managed to get something working with linear gradients that I think achieves the WebKit alpha appearance.
13:37
<annevk>
Which I think emilio has argued for.
13:38
<annevk>
Luke Warlow: oh, that might be a good replacement for my clipping thing if it works well. Would create less layers.
13:38
<Luke Warlow>
Regarding magic I more meant that base appearance could be defined entirely through UA stylesheet targeting the element and it's pseudo. No need for anything extra. But yeah there's more work needed to be fully free of magic.
13:39
<annevk>
I thought gradients wouldn't work due to arbitrary resizing. But I didn't play with them.
13:40
<Luke Warlow>
https://github.com/w3c/csswg-drafts/issues/11837#issuecomment-2705108403 This was what I prototyped in a custom element and it seems to work but it's possible I've just scratched the surface and it doesn't actually replicate everything.
13:42
<annevk>
Nice, that might well work.
13:48
<Luke Warlow>
And it might not actually remove magic if we decide that appearance: auto has to be behave as a replaced element without addressable inner parts.
Fwiw the inner parts are already addressable in all engines. Just via prefixed pseudos. I didn't think they were web exposed either but they are. Idk if that changes things at all.
13:51
<annevk>
Yeah I know. How appearance: auto gets standardized very much remains to be seen.
13:52
<annevk>
Noam Rosenthal: I don't see your response to https://github.com/whatwg/html/pull/10657#pullrequestreview-2515171306?
13:53
<annevk>
I guess I can do it.
14:09
<annevk>
Hmm, there's also no PR to rename the tests away from tentative. I'm going to leave that for someone else as hopefully it's just a rename, but Dominic Farolino and Noam Rosenthal please remember that for next time. If you want something to land it really helps if the entire checklist is actually done.
14:18
<Dominic Farolino>
What is the formatting thing? Was it https://github.com/whatwg/html/pull/10657#pullrequestreview-2513609939?
14:19
<Dominic Farolino>
That had been addressed a while ago but I just marked it resolved now. I can't find any other formatting comments though annevk
14:42
<Dominic Farolino>
Thanks for merging annevk. CL to move tests out of /tentative is up for review..
15:23
<annevk>
Dominic Farolino: formatting was https://github.com/whatwg/html/pull/10657/commits/39b3664e9e0ee00dbc3ebf4446b52d8734a5eda3
15:24
<annevk>
(You might want to review that since nobody else has...)
16:09
<Dominic Farolino>
annevk: The <dt> wrapping you did conflicts with wrapping guidance I've heard from Domenic about not wrapping specifically those elements (out of stylistic preference IIRC). I don't have strong opinions, but the wrapper tool follows that guidance (keeping <dt> content on one line).
16:35
<annevk>
I think that's likely the case for <dl class=domintro> <dt>s, but not all.
16:36
<annevk>
Anyway, good to know that case isn't covered by tooling.
23:22
<Domenic>
Also for dl class=props at least, so I think I generalized the advice