| 00:29 | <Hixie> | a-ja: thanks |
| 01:58 | <GPHemsley> | TabAtkins: If a `display: list-item' element does not also have an explicit counter associated with it, should there be a default counter that increments? |
| 01:59 | <GPHemsley> | "Additionally, list items automatically increment the special list-item counter. Unless the counter-increment property manually specifies a different increment for the list-item counter, it must be incremented by 1 on every list item, at the same time that counters are normally incremented." |
| 01:59 | GPHemsley | takes this as a yes. |
| 03:35 | <Itprotj> | Hey guys, on verifying my HTML5 Website I'm getting a: |
| 03:35 | <Itprotj> | Line 7, Column 111: Bad value google-translate-customization for attribute name on element meta: Keyword google-translate-customization is not registered. |
| 03:35 | <Itprotj> | …tomization" content="a940027e7f997750-6e3cf3faa4816ec1-g9f154a7bf834cf45-13" /> |
| 03:35 | <Itprotj> | I've checked the WHATWG wiki and "google-translate-customization" is an allowed metadata name but still it does not verify.. can anyone help please? |
| 03:44 | <Hixie> | Itprotj: it can take some time for the validators to update |
| 03:46 | <Itprotj> | Thanks Hixie, I noticed there was at least one person that had a similar issue and reported it mid 2013 but he was told the problem was "fixed" |
| 03:47 | <Itprotj> | Alas I shall wait, fingers crossed it doesnt take long. I use the W3 validator too |
| 03:50 | <MikeSmith> | Itprotj: I will add that to the validator later today or tomorrow |
| 03:50 | <dekiss> | hm are custom meta tags part of the spec? |
| 03:52 | <MikeSmith> | Itprotj: ping me here again tomorrow or so to remind me, if I've not gotten to it yet |
| 04:01 | <Itprotj> | Thanks Mike, Will do! |
| 17:26 | <MikeSmith> | Itprotj: I don't actually find any documentation about meta name="google-translate-customization" at https://support.google.com/translate/?hl=en or anywhere else |
| 17:35 | <rektide> | now that HTML has opted to free itself from the shackles of XML, why can <script/> tags not be self-closing? |
| 17:35 | <rektide> | so much ugly |
| 17:36 | <rektide> | so little good reason |
| 17:36 | <tantek> | the usual, backward compat, presumably. |
| 17:37 | <rektide> | so, free from shackles of XML, something else entirely, and yet only with regards to namespaces |
| 17:37 | <rektide> | i want my money back |
| 17:37 | <rektide> | the cake was a lie |
| 17:38 | <rektide> | i'd love if someone could imagine a use case that would actually break |
| 17:38 | <rektide> | because i cannot think of a place where anyone wouldn't close script |
| 17:39 | <rektide> | fix <script> tag, make it not the tag that hit every ugly branch on the DTD on the way down |
| 17:50 | <gsnedders> | rektide: WebKit used to allow self-closed script elements, they had a fair bit break because of it. |
| 18:10 | <MikeSmith> | self-closing tags are XML-think |
| 18:37 | <wefo> | What exactly does clearRect do? |
| 18:37 | <wefo> | What does "clearing" a rectangle mean? |
| 18:37 | <wefo> | I always rectFill with #000. |
| 18:38 | <wefo> | Because I want to be sure it "clears" with black. |
| 18:38 | <wefo> | What does clearRect do? |
| 19:18 | <jgraham> | (foolip++)**N for N>>1 |
| 19:26 | <jgraham> | MikeSmith: Can you do the last bit of https://critic.hoppipolla.co.uk/r/590, please? |
| 20:09 | <wefo> | What exactly does clearRect do? What does "clearing" a rectangle mean? I always rectFill with #000. Because I want to be sure it "clears" with black. What does clearRect do? |
| 23:59 | <gsnedders> | Ergh, do we have to change UTF-8 to utf-8? It's uppercase almost everywhere, and we do a case-insensitive match, so it's not like the normative form matters much — may as well pave-the-cowpath (and be consistent with earlier standards) and call it UTF-8. |
| 23:59 | <Hixie> | change where? |
| 23:59 | <Hixie> | i call it UTF-8 |