| 00:07 | <a-ja> | TabAtkins, have a sec to look at a css compatibility issue? |
| 00:08 | <a-ja> | TabAtkins, ^^^ https://jsfiddle.net/9c2qvh6h/2/ |
| 00:12 | <TabAtkins> | Yeah, I guess those properties aren't on our list of things that work for ::first-letter. |
| 00:12 | <TabAtkins> | (Your note implies that stroke works in ::first-letter, but it doesn't seem to for me.) |
| 00:15 | <a-ja> | Version 62.0.3202.94 (Official Build) (64-bit), with experimental properties enabled |
| 00:15 | <a-ja> | win10 |
| 00:19 | <TabAtkins> | Ah, I'm on 61 but with a pending update. I'll reboot and try again. |
| 00:19 | <a-ja> | i.e. "Experimental Web Platform features"...same if enabled |
| 00:19 | <a-ja> | k |
| 00:22 | <TabAtkins> | Nah, still not getting stroke to work on ::first-letter. Mind updating the fiddle to a version that shows off stroke working but not fill, just to make sure I'm not messing up something obvious? |
| 00:25 | <a-ja> | hmmm....looks same in chromium build from today...-webkit-text-stroke-color/width work on ::first-letter |
| 00:26 | <TabAtkins> | (By the by, it's cool and awesome that WK invented *two* different non-standard ways to fill text, one for colors and a completely different one for images.) |
| 00:26 | <a-ja> | same symptom for me for months...just got around to documenting and saying something |
| 00:26 | <TabAtkins> | Again, tho, could you update the fiddle to a state that works for you, so I can check on my own. ^_^ |
| 00:26 | <a-ja> | indeed :/ |
| 00:30 | <a-ja> | wfm on edge & gecko...stroke/fill wfm on non-first letter on blink, stroke wfm on first-letter on blink, but not fill |
| 00:31 | <a-ja> | talking the -webkit compat properties, not the "standard" ones nobody supports yet |
| 00:33 | <a-ja> | ::first-letter fills parse ok in inspector, but don't paint accordingly |
| 00:34 | <TabAtkins> | a-ja: Seriously for real, just update the fiddle so I can look at the exact same thing you're looking at. |
| 00:36 | <a-ja> | TabAtkins, nothing really to change, but just made heading bigger so it's more obvious |
| 00:37 | <a-ja> | https://jsfiddle.net/9c2qvh6h/5/ |
| 00:37 | <TabAtkins> | That fiddle still does not style the ::first-letter stroke. |
| 00:41 | <a-ja> | hmm...inherits for me, in chromium, canary, dev, beta, & release |
| 00:41 | <TabAtkins> | I mean there is literally no property in the ::first-letter block that styles the stroke. |
| 00:42 | <TabAtkins> | Given that you're talking about the fact that Chrome apparently has stroking work in ::first-letter but not filling, I'm still unsure what you're looking at. |
| 00:44 | <TabAtkins> | What I see: the code sets fill and stroke styles on h1, then only sets fill styles on h1::first-letter. The result is filled green and stroked pink. |
| 00:45 | <TabAtkins> | What you seem to be saying: stroking on ::first-letter works, filling on ::first-letter doesn't. |
| 00:45 | <a-ja> | right |
| 00:45 | <TabAtkins> | Your code sample doesn't demonstrate that, so I'm extremely confused. |
| 00:49 | <a-ja> | show me that under heading "Pseudo ::first-letter element" in inspector...can't understand why you're not seeing it |
| 00:49 | <a-ja> | *shows |
| 00:55 | <TabAtkins> | Again, I'm talking about the *code in the jsfiddle CSS panel*. It does not style the stroke for the ::first-letter. |
| 00:55 | <TabAtkins> | (The first letter is pink-stroked, like the rest of the word, in my browser.) |
| 00:56 | <a-ja> | correct....as it should, inherits |
| 00:56 | <TabAtkins> | sure. but this does not demonstrate what you're trying to say, which is that stroke works on ::first-letter but fill doesn't. |
| 00:57 | <a-ja> | you're not seeing h1.compatibility::first-letter { |
| 00:57 | <a-ja> | -webkit-text-fill-color: blue; |
| 00:58 | <TabAtkins> | That's not a stroke property! |
| 00:58 | <a-ja> | no, it's not |
| 00:58 | <a-ja> | it's a fill property |
| 00:58 | <TabAtkins> | That correctly shows that Chrome does not pay attention to fill properties in ::first-letter. It says nothing about whether Chrome honors stroke properties. |
| 01:00 | <a-ja> | you just said the first-letter is pink stroked...so apparently it does |
| 01:00 | <a-ja> | but not fill |
| 01:01 | <TabAtkins> | The pink stroke is set in the same rule as the green fill, the plain `h1.compatibility` rule. |
| 01:02 | <a-ja> | and inherits to firstt-letter |
| 01:04 | <a-ja> | https://jsfiddle.net/9c2qvh6h/7/ <- has stroke explicitly on first-letter rather than inheriting...no difference |
| 01:05 | <TabAtkins> | You're setting it to the exact same value! You can't tell whether it has an effect or not!?! |
| 01:06 | <TabAtkins> | I need you to set the stroke color to something *not* pink, in the `h1.compatibility::first-letter` rule, and confirm that when you do that, you see the first letter's stroke change to the not-pink color. |
| 01:06 | <TabAtkins> | And then show me that fiddle. ^_^ |
| 01:08 | <a-ja> | https://jsfiddle.net/9c2qvh6h/9/ |
| 01:09 | <TabAtkins> | Thanks. ^_^ So in yours, the C has an orange stroke and green fill? |
| 01:10 | <a-ja> | green fill, pink stroke |
| 01:13 | <a-ja> | blue fill, orange stroke in edge & gecko |
| 01:17 | <a-ja> | https://jsfiddle.net/9c2qvh6h/10/ <= has paragraph text updated to match what i'm seeing now |
| 01:20 | <TabAtkins> | Ah, ok, yes, that confirms that we're seeing the same thing, finally. |
| 01:20 | <a-ja> | so, maybe 2 probs...need both -webkit stroke & fill props in first-letter special cases...and differences in inheritance |
| 01:23 | <a-ja> | TabAtkins, depending on bg colors, have to use shadows to work around it now |
| 01:24 | <a-ja> | and that's kinda fugly |
| 01:26 | <a-ja> | on the positive side...you support drop caps on 1st-letter!!! |
| 05:00 | <gyuyoung> | Hello, can I ask a question regarding a status of isProtocolHandlerRegistered in the custom handlers specification? |
| 05:00 | <gyuyoung> | I found that isProtocolHandlerRegistered in the html5.2 specification though, it looks the latest specification of whatwg doesn't include it. |
| 05:00 | <gyuyoung> | - https://www.w3.org/TR/html52/webappapis.html#dom-navigatorcontentutils-isprotocolhandlerregistered |
| 05:00 | <gyuyoung> | - https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers |
| 05:00 | <gyuyoung> | So I wonder if isProtocolHandler is added to the specification or will be added to whatwg. Anyone know about it? |
| 05:19 | <MikeSmith> | gyuyoung: isProtocolHandlerRegistered is part of the registerContentHandler() feature that was removed from HTML a couple months ago |
| 05:20 | <MikeSmith> | the fact that the W3C copy still has it is a bug |
| 05:20 | <MikeSmith> | if you care to get that fixed, you can file a bug in the issue tracker for the W3C copy |
| 05:21 | MikeSmith | looks for the change that dropped registerContentHandler() |
| 05:22 | <MikeSmith> | https://github.com/whatwg/html/commit/b143dbc2d16f3473fcadee377d838070718549d3 |
| 06:13 | <gyuyoung> | MikeSmith: Thank you for the information. If specfication still has it, I wanted to implement it on Chromium. |
| 12:25 | <ondras> | so |
| 12:25 | <ondras> | 'If any of the strings in scriptURL’s path contains either ASCII case-insensitive "%2f" or ASCII case-insensitive "%5c", reject promise with a TypeError and abort these steps.' |
| 12:26 | <ondras> | what makes these (urlencoded) slashes so special? |
| 12:26 | <ondras> | (https://w3c.github.io/ServiceWorker/#start-register-algorithm) |
| 12:41 | <annevk> | ondras: prolly worth raising an issue on; should at least have a note, but might just be bogus |
| 12:41 | <annevk> | gyuyoung: isProtocolHandlerRegistered() has some privacy issues |
| 12:42 | <ondras> | interestingly enough, the / |
| 12:42 | <ondras> | /\ test is mentioned twice |
| 12:42 | <ondras> | in point 3 and point 7 |
| 12:42 | <annevk> | gyuyoung: makes fingerprinting a little easier, which I think is why it was blocked, though arguably that's also exposed through just following a link with a protocol handler |
| 12:42 | <annevk> | ondras: different URLs |
| 12:42 | <ondras> | I see |
| 12:43 | <ondras> | and both are forbidden from having encoded slashes |
| 13:15 | <ondras> | service worker question: is it possible to delay the .register() promise until the worker is installed, i.e. its "install" event finishes? |
| 13:16 | <annevk> | ondras: I don't think so |
| 13:16 | <ondras> | annevk: okay, thanks |
| 13:43 | <annevk> | Philip`: do you happen to have an image that has a width and height but cannot decode? |
| 14:01 | <ondras> | hmmh, [cache, response] = await Promise.all([caches.open(), fetch(request)]) |
| 14:02 | <ondras> | sounds like a more "performant" version of the traditional nested recipe |
| 14:02 | <ondras> | is something like this encouraged/useless/incorrect ? |
| 14:04 | <annevk> | ondras: https://jakearchibald.com/2014/offline-cookbook/#cache-network-race |
| 14:05 | <ondras> | interesting |
| 14:05 | <ondras> | yet not exactly the one I posted |
| 14:05 | <ondras> | this example has match/fetch in parallel |
| 14:05 | <ondras> | I used "only" open/fetch, so this would be the cache miss scenario |
| 14:17 | <jgraham> | For the record, "agent" is a spectacularly poor choice of name |
| 14:18 | <annevk> | I'd love to know why they went with that too |
| 14:18 | <annevk> | Continent was much nicer |
| 14:22 | <jgraham> | They could have picked almost any other term and it wouldn't have been so confusing. |
| 14:38 | <wanderview> | JakeA: do you have any thoughts on whatwg mailing list message titled "How to handle Session Expiry in ServiceWorker"? |
| 14:39 | <wanderview> | JakeA: seems like maybe a legit issue, but the reporter is banned from the github repo |
| 14:39 | <wanderview> | annevk: ^^^ |
| 14:41 | <annevk> | wanderview: anything involving credentials should involve UX so I don't see why credentials.get would just work |
| 14:42 | <annevk> | wanderview: https://w3c.github.io/webappsec-credential-management/#framework-credential-management even says it's restricted to windows |
| 15:13 | <wanderview> | annevk: ok |
| 21:06 | <MikeSmith> | TabAtkins: with Bikeshed for a W3C FPWD, how do I control what shows up in the “Status of the document” section? |
| 21:08 | <MikeSmith> | specifically, is there some way to get it to generate appropriate boilerplate? |
| 21:08 | <MikeSmith> | right now it shows nothing at all |
| 21:08 | <MikeSmith> | fg |
| 21:08 | <MikeSmith> | oofs |
| 21:10 | <MikeSmith> | hmm this is for a Web Payments WG publication and I see bikeshed/boilerplate/web-payments/status-FPWD.include but it’s not being used for some reason |
| 21:21 | <TabAtkins> | MikeSmith: I'll check when I get back to my house |
| 21:21 | <MikeSmith> | TabAtkins: thanks ー I got it working by putting a <div data-fill-with="status"></div> element in there |
| 21:22 | <MikeSmith> | dunno if that’s the right/best-practice way to do it or not, but it worked :) |
| 21:22 | <TabAtkins> | That should be in their header boilerplate... |
| 21:23 | <TabAtkins> | (it is the right way to include a status, but it should be in the boilerplate so you don't have to write it in manually) |
| 21:26 | <a-ja> | TabAtkins, if you've opened a bug/issue/whatever about the ::first-letter fill stroke thing we discussed yesterday...url please. tks |
| 21:27 | <TabAtkins> | I have not, I'm not sure what you wanted. It's a proprietary property, there's no spec about whether it should work in ::first-letter or not. |
| 21:28 | <a-ja> | TabAtkins, the -webkit properties are in the compatibility spec |
| 21:28 | <TabAtkins> | (Also I'm on vacation and very carefully control what sort of with I allow myself to do) |
| 21:28 | <TabAtkins> | Ah, haven't paid a ton of attention to the compat spec |
| 21:29 | <a-ja> | though i'm aware that what properties work on ::first-letter is up to vendor |
| 21:29 | <a-ja> | TabAtkins, sry....enjoy your turkey day |
| 21:29 | <TabAtkins> | I mean, if we allow 'color', there's no good reason to not allow fill/stroke |
| 21:31 | <a-ja> | TabAtkins, topic for next week :) |
| 23:11 | <wanderview> | annevk: I guess credentials.get() has a "silent" mediation mode... would be it make sense for that to be used in the service worker with out a window? |
| 23:13 | <jyasskin> | wanderview: I think 'yes'. mkwst is probably a good person to check with though. |