| 04:38 | <ljharb> | * i think I’ve reported that one before :-/ i usually just email Patrick and cc samina. Feel free to do so and cc me, or else i can do it later today (or this weekend, or monday) |
| 21:33 | <Chris de Almeida> | anyone know where I can find the full changelog for Chrome 126 ? the blog-style changelog doesn't account for a regression I'm seeing |
| 21:36 | <shu> | you want the list of commits? |
| 21:37 | <Chris de Almeida> | I'll take whatever I can get 🙂 |
| 21:39 | <shu> | probably easier to say what your regression is |
| 21:42 | <shu> | otherwise this is the branch head for 126, good luck: https://chromium.googlesource.com/chromium/src.git/+log/refs/branch-heads/6478 |
| 21:45 | <Chris de Almeida> | iframe load event not firing on bound listener |
| 21:49 | <Chris de Almeida> | our code has been stable for... 5 years at least? and it's only started failing in Chrome 126, passes in FF and in Chrome <126. we do a simple bind to load for an iframe, then set src and that load event tells us the page/iframe is loaded. that has just started to fail intermittently, but consistently |
| 21:52 | <Chris de Almeida> | the page is loaded. I can see it.. but the load event doesn't fire |
| 21:52 | <shu> | file an issue? |
| 21:52 | <shu> | someone hopefully triages and tries to repro, and if they can, then try to bisect |
| 21:52 | <Chris de Almeida> | sure.. I was hoping to track down any noticeable (related) changes in the release first. prefer not to throw stuff over the wall right away |
| 21:53 | <shu> | https://chromestatus.com/roadmap if it's at feature granularity and the feature owner remembers to update |