| 03:30 | <MikeSmith> | about the data at https://www.chromestatus.com/features on implementation status in other UAs, does anybody know wherethe source for that data maintained? |
| 11:26 | <joynal> | Hello everyone |
| 12:43 | <espadrine> | Hi, is there a non-legacy reason for input.files to be readonly? |
| 12:46 | <espadrine> | Maybe the idea is for it to be allowed to append File objects once input.files no longer yields a FileList, but an Array instead? |
| 12:52 | <nox> | I think I found another bug with Range.createContextualFragment. |
| 12:53 | <nox> | Step 4 says to unmark all scripts in fragment node as already started, so that when they get executed when inserted in a document afterwards |
| 12:53 | <nox> | But https://html.spec.whatwg.org/multipage/scripting.html#script-processing-model:prepare-a-script-4 says that we should only prepare scripts when connecting them in a tree if it isn't marked as parser-inserted. |
| 12:54 | <nox> | Step 4 should probably say that they should be marked as parser-inserted again. |
| 12:54 | <nox> | Because step 7 of "prepare" says 'If was-parser-inserted is true, then flag the element as "parser-inserted" again, and set the element's "non-blocking" flag to false.'. |
| 14:42 | <espadrine> | Looks like input.files is not actually readonly on Chrome. |
| 14:42 | <espadrine> | It still is conformant on Firefox, though. |
| 15:26 | <annevk> | espadrine: can you construct a FileList somehow? |
| 15:27 | <annevk> | espadrine: there are various open issues on this, iirc |
| 15:27 | <espadrine> | annevk: Not through a constructor, although you can fetch one from a different input element or from a drop zone. |
| 15:29 | <espadrine> | I’d welcome a link to an issue; I tried searching for one. |
| 15:30 | <annevk> | espadrine: against IDL perhaps? On my phone, so can't really search well |
| 18:13 | <silverdust> | boolean attributes are best without values ain't it? Can I get a reference link to prove this too? |
| 18:58 | <nox> | silverdust: http://heycam.github.io/webidl/#dfnReturnLink-2 |
| 18:58 | <nox> | Oh wait, attributes, I read argument. |
| 19:01 | <espadrine> | re: input.files, I made an issue https://github.com/whatwg/html/issues/1391 |
| 19:51 | <silverdust> | yes attributes. Is there any good reason to assign values to attributes like required, checked? Perhaps some browser support? |
| 22:34 | <Domenic> | silverdust: https://html.spec.whatwg.org/multipage/infrastructure.html#boolean-attributes might help. |
| 22:34 | <Domenic> | silverdust: there is no reason to require values; you can use the name of the attribute as a value if you want but it does nothing different than the empty string or omitting the value entirely |
| 22:39 | <silverdust> | Thanks Domenic |