| 12:23 | <akaster> | gotcha. I opened https://github.com/w3c/resource-timing/issues/414 for this one. Luke opened two more issues he found in Ladybird's initial implementation over in the fetch repo as well. |
| 13:07 | <zcorpan> | 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 |
| 13:47 | <annevk> | zcorpan: shouldn't it be added at that point? |
| 13:54 | <zcorpan> | annevk: I thought people may want to customize the inner content also for a regular <input type=color> |
| 14:27 | <smaug> | I wonder if there is some addon which clicks "Load more..." as long as there is one in a github pr/issue |
| 14:28 | <smaug> | Maybe I should try to use some AI tool to generate such addon |
| 14:33 | <zcorpan> | I would be a user for sure |
| 15:12 | <annevk> | zcorpan: I guess, but you already have ::before and ::after to play with and possibly more. Seems reasonable to discuss in an issue though, especially if there's some precedent in a UA style sheet. (I don't think there is in ours in this case.) |
| 15:14 | <annevk> | Last time this was discussed Mike pointed out https://github.com/dlvhdr/gh-dash though looking at it now that's more of a CLI thing. |
| 15:23 | <sideshowbarker> | Yeah, that thing is “TUI” (terminal UI — like a GUI but in the terminal) |
| 15:24 | <sideshowbarker> | But if you’re OK with using the shell/CLI to do stuff, you don’t even need that |
| 15:24 | <sideshowbarker> | You can instead just use the GitHub CLI |
| 15:24 | <sideshowbarker> | gh pr view |
| 15:24 | <sideshowbarker> | Example: |
| 15:25 | <sideshowbarker> | That’ll show you all the comments — without you needing to expand anything |
| 15:26 | <zcorpan> | @annevk yeah, I can file an issue. It seems ::before and ::after work in webkit and chromium, but not gecko. input[type=color] { content: url(image) } replaces the color well in webkit and chromium, does nothing in gecko. |
| 15:26 | <sideshowbarker> | And also note that it just shows the comments — minus all the other intervening noise that GitHub dumps into PR/issue discussions |
| 15:27 | <sideshowbarker> | I mean minus the dozens of things like this:
|
| 15:27 | <annevk> | zcorpan: well you'd have to appearance:base first, right? |
| 15:28 | <annevk> | There is also the replaced element concern for appearance:auto, but that seems like a separate topic. |
| 15:28 | <zcorpan> | Hmm yeah |
| 15:29 | <sideshowbarker> | For the web UI, even if you did have some addon that would click “Load more…” for you, the web UI would still be showing you all that noise |
| 15:29 | <sideshowbarker> | …you’d need another addon to filter out all the noise |
| 15:30 | <sideshowbarker> | But the gh cli just omits all the stuff to begin with, and all the comments at one. You just page through it less or whatever you have as your pager in your shell |
| 15:31 | <sideshowbarker> | Anyway, I recommend trying that gh pr view thing at least |
| 23:19 | <smaug> | mfreed: still trying to find when the focus fixup happens |
| 23:19 | <smaug> | around rendering looks like |
| 23:19 | <smaug> | isn't that broken? |
| 23:20 | <smaug> | key events may come in between something becoming inert and rendering steps |
| 23:52 | <Domenic> | 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. |
| 23:53 | <Domenic> | https://github.com/whatwg/html/pull/8392 https://github.com/whatwg/html/issues/3847 https://github.com/whatwg/html/issues/8225 |
| 23:54 | <Domenic> | The current model is basically a request from Emilio |