| 01:27 | <Domenic> | We do use <i> for references from one algorithm to a parameter of another algorithm. A modern example of that is all the references to optional named parameters of https://html.spec.whatwg.org/#navigate . |
| 01:28 | <Domenic> | Same-origin fallback flag looks like an old version of that before we had our modern conventions (which include a <dfn><var> at the declaration site and an <a><i> at the call site) |
| 01:30 | <Domenic> | Separately, HTML has lots of random <i> usage from a former editor that I don't really understand, e.g. missing value default/invalid value default, mutable, etc. |
| 06:51 | <zbaviles> | // 1. Find the button element (assuming it has the ID "myButton")const myButton = document.getElementById("myButton");// 2. Add an event listener for the "mouseover" eventmyButton.addEventListener("mouseover", function() { // 3. Change the background color using CSSOM myButton.style.backgroundColor = "yellow"; }); |
| 07:07 | <zbaviles> | // 1. Find the button element (assuming it has the ID "myButton")const myButton = document.getElementById("myButton");// 2. Get the user agent stringconst userAgent = navigator.userAgent;// 3. Check if the user agent string indicates a desktop browserif (/Windows|Macintosh|Linux|X11/.test(userAgent)) { myButton.addEventListener("mouseover", function() { // 4. Change the background color using CSSOM if the user is on a desktop browser myButton.style.backgroundColor = "yellow"; });} |
| 23:27 | <Luke Warlow> | Is there a particular reason why you can't call .showPopover() an open modal dialog, but on an open non-modal dialog it works? Seems like it should probably throw in both cases? |