| 01:20 | <Domenic> | An important question to ask is "who is consuming this markup". Are you trying to make it easier to read if someone is editing it in a text editor? <span class="author"> or <span data-author> seem reasonable. Are you trying to style it? Same thing. Are you trying to make it easy to consume by other parts of your code (e.g. JS)? Same thing. Are you trying to make it more accessible? This isn't applicable; no accessibility |
| 01:20 | <Domenic> | technology distinguishes between authors, titles, editions, years of publication, or ISBN numbers vs. any other run of text. |
| 01:20 | <Domenic> | The case where you need specific standardized markup patterns here would be if you want other software, which you don't write or control, to be able to scrape your page and extract this data. In those cases schema.org is used by at least some of that software, so it might be a good fit for you. |
| 01:22 | <tejr> | Thanks Domenic, food for thought |
| 01:29 | <a-ja> | oh yeah, forgot earlier work: http://microformats.org/wiki/citation and http://microformats.org/wiki/h-cite |
| 01:30 | a-ja | thanks Domenic for the additional context |
| 14:28 | <annevk> | So I look into some Referrer Policy stuff to see how it dealt with inheritance and the tests are just broken? E.g., referrer-policy/generic/inheritance/iframe-inheritance-data.html |
| 14:38 | <jgraham> | Which kind of broken? Not working at all or wrong in what they test? |
| 14:38 | <jgraham> | mkwst might know more about those tests |
| 14:39 | <annevk> | jgraham: not really working |
| 14:40 | <annevk> | And I can fix all these things, but I kinda feel tired from having to clean up all the mess and not being able to do my own things because of that |
| 14:42 | <jgraham> | YEah, I understand :/ |
| 14:42 | <jgraham> | jochen⊙co seems to have written that test |
| 14:42 | <jgraham> | Came from a Chromium import |
| 14:51 | <jgraham> | (and also fails in Chrome, which is surprising) |
| 15:56 | <annevk> | jochen__: ^ if you have time |
| 20:39 | <ondras> | hm, I *think* I found a firefox bug - or perhaps the behavior is correct? |
| 20:39 | <ondras> | https://jsfiddle.net/8fq26dLa/1/ |
| 20:39 | <ondras> | it only happens with touch |
| 20:39 | <ondras> | in Firefox, there is no "pointerup" fired when the button is touched (up+down) |
| 20:40 | <ondras> | probably because the button gets removed during the pointerdown handler |