| 01:01 | <MikeSmith> | smaug____: yeah html/semantics/embedded-content/the-canvas-element directory |
| 01:01 | <MikeSmith> | smaug____: what kind of tests were you expecting there? |
| 01:01 | <smaug____> | oh there |
| 01:01 | <smaug____> | didn't find that |
| 01:01 | <MikeSmith> | well there are not many there either |
| 01:01 | <smaug____> | MikeSmith: someone was asking where to add new tests |
| 01:01 | <MikeSmith> | OK |
| 01:02 | <MikeSmith> | I guess the spec does not have many requirements in that section that are not requirements of the 2dcontext API |
| 01:02 | <smaug____> | I suggested html/dom |
| 01:02 | <MikeSmith> | ah |
| 01:03 | <MikeSmith> | there are no canvas tests under there |
| 01:04 | <smaug____> | sure |
| 01:04 | <smaug____> | but that doesn't really say much |
| 01:04 | <MikeSmith> | well except the HTMLCanvasElement interface |
| 01:04 | <MikeSmith> | (assuming that’s what it’s called) |
| 01:04 | <smaug____> | but ok, I commented that html/semantics/embedded-content/the-canvas-element could be used |
| 01:04 | <smaug____> | thanks |
| 01:05 | <MikeSmith> | cheers |
| 01:06 | <MikeSmith> | reading https://lists.webkit.org/pipermail/webkit-dev/2017-February/028694.html “Upstreaming Tests from WebKit to Web Platform Tests” from rniwa |
| 02:50 | <MikeSmith> | https://www.w3.org/community/httpslocal/ |
| 09:24 | <MikeSmith> | zcorpan: FYI https://bugzilla.gnome.org/show_bug.cgi?id=778192 (request to have libxslt output <!DOCTYPE html) if <xsl:output method="html" version="5"> (as Saxon already does) |
| 09:25 | <MikeSmith> | zcorpan: also I discovered that if you use <xsl:output doctype-system="about:legacy-compat"> with libxslt it will output <!DOCTYPE html> |
| 09:25 | <MikeSmith> | due to https://bugzilla.gnome.org/show_bug.cgi?id=747301 |
| 09:26 | <MikeSmith> | but if you use <xsl:output doctype-system="about:legacy-compat"> with Saxon or other XSL implementations, of course you will get a literal SYSTEM "about:legacy-compat" in the doctype, as you’d expect |
| 09:27 | <MikeSmith> | I don’t have much hope that Daniel Veillard will implement my request unless I provide a patch (and maybe not even then) |
| 09:28 | <MikeSmith> | But I prefixed the bug title with “Please consider supporting…” so maybe that will help :) |
| 09:31 | <zcorpan> | MikeSmith: 👍 |
| 12:33 | <zcorpan> | https://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F looks like steps 7, 8, 9 are kinda backwards now |
| 15:08 | <Domenic> | Yeah it'd be good to get that updated |
| 21:28 | <TabAtkins> | SimonSapin: Dammit Simon, you ninja'd me by like 30 seconds. I was almost done with a nearly identical response. ^_^ |
| 21:28 | <SimonSapin> | haha |
| 21:29 | <SimonSapin> | TabAtkins: so how do you feel about implementing it? |
| 21:29 | <TabAtkins> | Writing up that response now - please god do it. |
| 21:30 | <SimonSapin> | TabAtkins: we had a servo PR for this last year, but it was kind wrong in lots of ways and I never got around to fixing it up. Then it got bitrotted enough that we closed it. |
| 21:30 | <SimonSapin> | (And it’s not like servo was gonna drive adoption. But now with Stylo it could be another story…) |
| 21:42 | <nox> | SimonSapin: Implementing what? |
| 21:43 | <SimonSapin> | nox: MQ4 new syntax |
| 21:43 | <SimonSapin> | https://lists.w3.org/Archives/Public/www-style/2017Feb/0035.html |
| 21:43 | <TabAtkins> | Specifically, adding the relational operators (<, >, <=, >=) to MQ rather than using min-*/max-* prefixes on things. |
| 21:44 | <nox> | Nice. |
| 23:57 | <smaug> | element's browsing context isn't something defined anywhere, right? |