| 02:09 | <MikeSmith> | Domenic: about the MDN annos in the HTML spec, what do you think about switching to using JavaScript to position them? |
| 02:10 | <MikeSmith> | I mean rather than doing what we are now, trying to append them to the right node in the generated output at build time |
| 02:11 | <MikeSmith> | specifically we can use getBoundingClientRect().top + window.scrollY to put align them with the actual elements whose dfn they annotate |
| 02:11 | <MikeSmith> | that is how TabAtkins does it in Bikeshed for the Can I Use annos |
| 02:15 | <TabAtkins> | Yeah it's way way easier that way |
| 02:17 | <TabAtkins> | Don't have to worry about using an inappropriate element just so it doesn't autoclose <p>, etc |
| 03:26 | <MikeSmith> | TabAtkins: yeah, exactly |
| 03:27 | <MikeSmith> | in the wattsi code that I wrote for the MDN annotations for HTML, the code for trying to get the annos into the right place in the DOM was by far the mostly time-consuming and un-fun to write |
| 03:28 | <MikeSmith> | and it was the most contentious part of the review process too |
| 06:26 | <Domenic> | MikeSmith: seems pretty bad to make them depend on JS IMO... especially in a spec the size of HTML. I thought we got pretty far in https://github.com/whatwg/wattsi/pull/95. |
| 06:40 | <annevk> | I'm somewhat surprised CSS doesn't have a way to tackle this, has that been discussed? (Not going to solve it for us, but...) |
| 06:42 | <MikeSmith> | Domenic: OK I can look back at that PR |
| 08:42 | <annevk> | MikeSmith: wanna approve https://github.com/whatwg/whatwg.org/pull/305 too? |
| 08:42 | MikeSmith | looks |
| 08:43 | <MikeSmith> | ah cool yeah |
| 08:45 | <annevk> | The only thing left to do is generate some page that lists the workstreams |
| 08:45 | <annevk> | And I guess link it from places |
| 18:55 | <TabAtkins> | Could I ask for a quick r+ and merge? Obvious markup error in webidl https://github.com/heycam/webidl/pull/853 |