| 00:27 | <MikeSmith> | wow, Blink/Chrome style guidelines recommend (prohibit in some cases?) against use of `const`? because of design limitations in V8 it seems |
| 00:29 | <MikeSmith> | https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/MJhTok8Usr8/XCrkisaBBQAJ |
| 00:30 | <MikeSmith> | > In a recent CL, I was told that the DevTools still do not use const and existing usage is being removed due to V8 deoptimization concerns. |
| 08:57 | <zcorpan> | Is it possible to have a wiki page redirect to an external url? And how do I edit the links in the sidebar? |
| 09:38 | <strupo> | zcorpan: for linking to an external URL, see https://en.wikipedia.org/wiki/Wikipedia:Tutorial/Wikipedia_links#External_links_section |
| 09:39 | <strupo> | for editing the sidebar, just click the "edit" link on top of the page, and locate where the sidebar is to edit it |
| 09:39 | <zcorpan> | strupo: ideally I want the page to redirect, not just show a link |
| 09:40 | <strupo> | Well, I don't know if you can do that |
| 09:40 | <zcorpan> | ok |
| 09:40 | <strupo> | It can redirect to another wiki article, but to an external URL... I don't think so. |
| 09:42 | <zcorpan> | clicking edit gets me to https://wiki.whatwg.org/index.php?title=Main_Page&action=edit but still don't see how to edit the "Code of Conduct" link in the left-hand sidebar |
| 09:44 | <strupo> | I think that's indepedent of which article you're seeing now |
| 09:45 | <zcorpan> | maybe I don't have editInterface permission. https://www.mediawiki.org/wiki/Manual:Interface/Sidebar |
| 09:49 | <GPHemsley> | https://wiki.whatwg.org/wiki/MediaWiki:Sidebar |
| 09:50 | <GPHemsley> | zcorpan: I've made you an admin |
| 09:50 | <zcorpan> | GPHemsley: thanks! |
| 09:50 | <GPHemsley> | there's probably some other folks around here who should have those rights |
| 09:51 | <GPHemsley> | this list seems short: https://wiki.whatwg.org/index.php?title=Special:ListUsers&group=sysop |
| 10:53 | <hasather> | https://html.spec.whatwg.org/#dom-form-elements says “The elements IDL attribute must return an HTMLFormControlsCollection rooted at the form element…”. But `elements` also includes any elements outside the form whose form owner is the form (<input form=“”>), so “rooted at the form elements” seems wrong to me. Or am I misreading it? |
| 14:00 | <GPHemsley> | annevk, Domenic, Sebmaster: Is there a particular organization to the urltestdata.json file that PRs should maintain? |
| 14:02 | <annevk> | GPHemsley: no 😟 |
| 14:04 | <GPHemsley> | cool, so I'll just go willy nilly |
| 14:09 | <GPHemsley> | annevk: How about preference for # or no # in comments? |
| 14:17 | <annevk> | GPHemsley: one of those for a following block is what I do |
| 14:18 | <GPHemsley> | well I added the comment string for the blocks, sure |
| 14:18 | <GPHemsley> | but some of them use a preceding # |
| 14:18 | <GPHemsley> | I opted not to, since it seems redundant |
| 14:44 | <GPHemsley> | https://github.com/w3c/web-platform-tests/pull/6238 |
| 14:46 | <nox> | GPHemsley: Out of curiosity, what's the purpose of writing "\u003E" rather than just >? |
| 14:47 | <GPHemsley> | the spec is explicit about bytes/code points, so this make it clear that they're there |
| 14:49 | <nox> | GPHemsley: But the parser won't ever see \u003E. |
| 14:49 | <GPHemsley> | I'm aware |
| 14:49 | <GPHemsley> | that's for the humans |
| 14:49 | <nox> | As a human I would rather read > than \u003E. |
| 14:54 | <GPHemsley> | and as a human, you are able to easily identify and distinguish between >›〉⟩〉? |
| 14:54 | <nox> | https://irccloud.mozilla.com/file/HNAyCCdJ/Capture%20d%E2%80%99e%CC%81cran%202017-06-14%20a%CC%80%2016.54.27.png |
| 15:01 | <GPHemsley> | uh huh, and which one is the one relevant to the test? |
| 15:54 | <nox> | GPHemsley: The first one. I wrote it just above soit was easy to distinguish it. |
| 15:54 | <nox> | I just don't see how that is an argument against a literal >, which is the obvious one. You wouldn't argue against writing a 'a' because it could be Latin or Cyrillic, would you? |
| 15:55 | <nox> | In the end, none of the tests actually show which character it is about, so as a human I have to look up the characters somewhere to know what the test is checking for. |
| 15:56 | <nox> | none of the expectations* |
| 16:18 | <GPHemsley> | I mean, I can change it if that's the consensus |
| 16:18 | <Domenic> | In case hasather comes back: that gives the definition of the elements IDL attribute, so since the definition says it's rooted at the form element, then no, elements cannot contain any elements outside the form. |
| 16:18 | <GPHemsley> | but I did it deliberately to highlight what it was testing: "If byte is less than 0x21 (!), greater than 0x7E (~), or is 0x22 ("), 0x23 (#), 0x3C (<), or 0x3E (>), append byte, percent encoded, to url’s query. " |
| 16:18 | <Domenic> | GPHemsley: nox: my opinion is it's up to the test author; I try not to let stylistic things get in the way of making authoring tests easy. |
| 16:19 | <nox> | Would be nice to give these tests a name then. |
| 16:19 | <GPHemsley> | 'Percent-encoded query and fragment' is the name |
| 17:57 | <Domenic> | hsivonen: I'm willing to devote some time to helping you land WPTs for encoding (including r12a's tests) if you can provide all the domain expertise. E.g. if you want to provide diffs to r12a's pull requests I can apply them and press the merge button. |
| 18:47 | <gsnedders> | Domenic, hsivonen: I can also spend some time reviewing them or changes to them, but last I looked I got lost in complexity |
| 21:16 | <Domenic> | tobie: https://github.com/heycam/webidl/pull/323 is ready to merge BTW :) |
| 21:18 | <tobie> | Domenic: yeah, I got started on adding tests for it and wanted to land both together, but the testing tool a little longer than expected. |
| 21:18 | <tobie> | Domenic: https://github.com/w3c/web-platform-tests/pull/6246 |
| 23:49 | <smaug> | https://html.spec.whatwg.org/multipage/semantics.html#attr-link-as |
| 23:49 | <smaug> | doesn't that mean that .as can be "featch" |
| 23:55 | <Domenic> | smaug: no. https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#reflecting-content-attributes-in-idl-attributes:enumerated-attribute |
| 23:56 | <smaug> | so? |
| 23:56 | <smaug> | "A potential destination is "fetch" or a destination which is not the empty string. " |
| 23:56 | <smaug> | er |
| 23:56 | <smaug> | fetch |
| 23:56 | <smaug> | that was typo, fetch, not featch |
| 23:57 | <Domenic> | oh. Then yes. |
| 23:57 | <smaug> | just reviewing some code and for some reason it returned "" when content attribute was "fetch" |
