|
`el.className` and `el.htmlFor` have such unusual names because `class` and `for` used to be reserved words in JS. That hasn't been true for property names for 10+ years. Firefox is experimenting with adding `el.class` and `el.for`, yay! https://github.com/whatwg/html/issues/9379#issuecomment-2357214793 5 comments
@sil here's a fun one: If you do onclick="…" then that code runs with up to three implicit `with` blocks. https://html.spec.whatwg.org/multipage/webappapis.html#getting-the-current-value-of-the-event-handler:~:text=If%20eventHandler%20is%20an%20element%27s,element%2C%20true%2C%20scope).  This week I learnt that there's a `parentElement`. I had just been using `parentNode` for so long, I didn't realise there was something else. Funnily enough it was Typescript that told me to use something other than `parentNode`. |
Gregory's Server
@jaffathecake this year has been a succession of discoveries of stuff which I have believed is true for years (sometimes decades) and I have never revisited. Radix parameter to parseInt()? Not required. NodeLists don't have .forEach? Yes they do. Property names are allowed to be reserved words? This is the latest surprise. Next someone will tell me that with{} is OK or something