| 15:38 | <zcorpan> | zcorpan: Yeah, looks like the server wedged itself yesterday morning. Kicking it now. |
| 17:08 | <c_a-g_o> | WTF is a popsicle? |
| 17:14 | <annevk> | zcorpan: could it be because it's not a generated document? ReSpec tends to have issues |
| 17:16 | <annevk> | zcorpan: hardlinking from DOM might be the way to go, same as we do for DOMHighResTimeStamp and friends |
| 17:16 | <zcorpan> | annevk: ah yeah maybe that's the issue. ok |
| 17:16 | <annevk> | I wish folks would stop using ReSpec, but then we still have Wattsi so... |
| 17:17 | <c_a-g_o> | wattsi ReSpec |
| 17:17 | <zcorpan> | Maybe bikeshed could use Webref instead of scraping? |
| 17:18 | <annevk> | There's an issue for that somewhere |
| 18:10 | <TabAtkins> | Yes, last time I worked on it I got 99% of the way thru but WebIDL was suddenly causing weird biblio entries that I coudl not figure out, so I stalled. Working on tangential code-quality stuff in the area instead right now, but it's in my OKRs for the quarter. |
| 18:12 | <TabAtkins> | emilio, krave: Yes, the CSS Values & Units spec is the defining doc for CSS's value grammar. (The Syntax spec just adds some additional bits for defining whole rules, which aren't covered by the V&U stuff since it's not needed.) |
| 18:13 | <TabAtkins> | zcorpan: Tho moving to WebRef is the correct idea, I'll note that Bikeshed subtly encouraging ReSpec users to actually publish a formatted document instead of inflicting the rest of us with the flash-of-plain-text spec is a Good Thing imo |
| 18:45 | <zcorpan> | TabAtkins: agreed |
| 19:29 | <zcorpan> | TabAtkins: filing issues on such specs might be more effective though, in this case the editors of the spec aren't the ones to feel the pain |
| 22:07 | <TabAtkins> | annevk or Domenic: the maplike/setlike @@iterator and forEach have text detailing where the methods live, depending on whether the interface is [Global] or not. https://webidl.spec.whatwg.org/#es-iterator The rest of the methods don't; they're defined to just live on the interface prototype object. https://webidl.spec.whatwg.org/#es-maplike It looks like this might get handled generically instead by the "interface prototype object" text https://webidl.spec.whatwg.org/#dfn-interface-prototype-object but the details of the algo confuse me so I'm not sure. Do y'all know if the distinctions in spec text are intentional, or just editorial slippage that should be aligned? |
| 22:08 | <짜요> | hello! I had a question while developing. I'm using title attribute related html5, but the number of characters seen by each browser is different. Chrome and edge are the same and safari shows more, I wonder Do you know how much the title attribute can show by browser? |
| 22:10 | <Domenic> | annevk or Domenic: the maplike/setlike @@iterator and forEach have text detailing where the methods live, depending on whether the interface is [Global] or not. https://webidl.spec.whatwg.org/#es-iterator The rest of the methods don't; they're defined to just live on the interface prototype object. https://webidl.spec.whatwg.org/#es-maplike It looks like this might get handled generically instead by the "interface prototype object" text https://webidl.spec.whatwg.org/#dfn-interface-prototype-object but the details of the algo confuse me so I'm not sure. Do y'all know if the distinctions in spec text are intentional, or just editorial slippage that should be aligned? |
| 22:11 | <Domenic> | Some previous PRs linked from https://github.com/whatwg/webidl/issues/467 |
| 22:11 | <TabAtkins> | Okay, I'm not touching the imperativeness yet, so I'll just leave it as-is. |