| 08:22 | <hsivonen> | did the LC poll reach quorum? |
| 08:32 | <abarth> | hsivonen: i think i've lost my ability to vote |
| 08:32 | <zcorpan> | abarth: the poll closed yesterday |
| 08:33 | <abarth> | (i was more explaining why I didn't participate) |
| 08:39 | <zcorpan> | hsivonen: do you have a clue as to how a questionmark appeared as favicon for your feed in my feedreader? |
| 08:47 | <hsivonen> | zcorpan: is your browser your feed reader? |
| 08:55 | <zcorpan> | hsivonen: yep, opera |
| 09:09 | <hsivonen> | zcorpan: could it be that you looked at my rel="shortcut icon" test cases and Opera decided to use the favicon declared in those files for any other URLs from hsivonen.iki.fi that don't have an explicit favicon? |
| 09:10 | <zcorpan> | hsivonen: it's indeed that icon. but opera doesn't show that icon when browsing your site, just the feed. weird |
| 09:10 | zcorpan | files a bug |
| 09:42 | <MikeSmith> | hsivonen: the poll did reach quorum, yeah |
| 10:02 | <zcorpan> | MikeSmith: for all documents? |
| 10:04 | <zcorpan> | heycam|away: wait what happened with sequence<T> and MessagePortArray? |
| 10:47 | <MikeSmith> | zcorpan: yeah, for all documents |
| 10:47 | <MikeSmith> | as far as I can tell |
| 11:18 | <MikeSmith> | any opinions on whether it would be a good idea to set up a mailbot that would automatically create HTML5 spec bugs from new messages posted to the public-html-comments list? |
| 11:18 | <MikeSmith> | that is, non-reply messages |
| 11:18 | <Ms2ger> | Hmm |
| 11:19 | <MikeSmith> | I can't see that it would be much of a problem as far as risk of malicious spam |
| 11:19 | <MikeSmith> | certainly not more than the current comment form |
| 11:20 | <MikeSmith> | because to post to that list, users basically need to first do the archive-approval step |
| 11:21 | <MikeSmith> | which essentially also works as an authentication mechanism to verify that they aren't spoofing an e-mail address |
| 11:22 | <MikeSmith> | the main problem I'd see is that some messages posted to that list may not actually be intended as comments |
| 11:22 | <MikeSmith> | but for those, it'd be easy enough to just move them to resolved-invalid |
| 11:23 | <MikeSmith> | so I guess it's a question of how much of them would be of that type |
| 11:23 | <MikeSmith> | what the signal-to-noise ratio would be |
| 11:24 | <Ms2ger> | I think there's little enough traffic to try it |
| 11:24 | <MikeSmith> | OK |
| 11:25 | <MikeSmith> | I can mess around with setting something up |
| 11:26 | <MikeSmith> | hmm |
| 11:26 | <MikeSmith> | as long as I'm not misunderstanding you |
| 11:26 | <MikeSmith> | Ms2ger: did you mean you think it's worth trying, or not worth trying? |
| 11:27 | <Ms2ger> | Worth trying |
| 11:27 | <MikeSmith> | ok |
| 11:27 | <MikeSmith> | thanks |
| 11:29 | <MikeSmith> | http://vkontakte.ru/photo63802_263023722?all=1 |
| 11:30 | <Ms2ger> | I do! |
| 11:32 | <MikeSmith> | heh |
| 11:33 | <MikeSmith> | I speak pidgin Javascript |
| 12:40 | <_bga> | gsnedders are you here? |
| 12:46 | <gsnedders> | _bga: yes |
| 12:47 | <_bga> | what proseccors is supported by carakan |
| 12:47 | <_bga> | i mean jit |
| 12:47 | <_bga> | only x86? |
| 12:49 | <gsnedders> | x86, x86_64, and ARM. |
| 12:50 | <_bga> | what about jvm bytecode? |
| 12:50 | <_bga> | as rhino |
| 12:50 | <gsnedders> | (Well, x86 with x87 (though this has never been shipped), x86 with SSE2, x86_64, ARM with/without VFP) |
| 12:50 | <gsnedders> | _bga: Why would we? |
| 12:51 | <_bga> | opera mobile |
| 12:51 | <gsnedders> | _bga: Opera Mobile is C++ |
| 12:53 | <_bga> | i thought its java |
| 12:53 | <_bga> | ok |
| 12:53 | <gsnedders> | _bga: We don't have two separate web browsers here. |
| 12:54 | <_bga> | only opera mini is java based? |
| 12:54 | <Philip`> | (So on x86 without SSE2 it'll disable the JIT entirely?) |
| 12:55 | <gsnedders> | Philip`: (Yeah) |
| 12:55 | <gsnedders> | _bga: Mini is just a thin-client, Presto runs on server. |
| 12:55 | <_bga> | understand |
| 12:56 | <Philip`> | (That seems unfortunate for some percents of users) |
| 12:57 | <gsnedders> | Philip`: (Everyone, except Chrome which just refuses to run, does that.) |
| 12:58 | <gsnedders> | Philip`: (And x86/x87 would effectively be yet another arch to support, maybe it'll be finished some day…) |
| 12:59 | Philip` | knows SpiderMonkey has x87 JIT but has no idea if/how it's exposed via the browser |
| 13:00 | <gsnedders> | Philip`: It does? |
| 13:00 | Philip` | knows because it had bugs that broke his SpiderMonkey-embedding game for non-SSE2 users :-( |
| 13:00 | <gsnedders> | Philip`: Are you sure it was doing that and not just using x87 for doubles in the interpreter? |
| 13:01 | <_bga> | i see superh is another popular processor |
| 13:01 | <_bga> | jscore and sm support it |
| 13:01 | <Philip`> | nanojit/Nativei386.cpp has paths for "if (!_config.i386_sse2)" etc |
| 13:02 | <gsnedders> | Philip`: Heh, I thought it didn't. JSC certainly doesn't. |
| 13:03 | <gsnedders> | _bga: SuperH seems to be being used less and less |
| 15:03 | <hsivonen> | TabAtkins: you wondered about double line breaks when copying from View Source |
| 15:03 | <hsivonen> | TabAtkins: double line breaks appear where a pre ends and a new one starts |
| 15:04 | <hsivonen> | TabAtkins: since pre serializes as a block, there's an extra line break |
| 15:05 | <hsivonen> | TabAtkins: there are multiple pre elements, because that way the bidi algorithm runs on smaller chunks |
| 15:05 | <hsivonen> | TabAtkins: https://bugzilla.mozilla.org/show_bug.cgi?id=649613 |
| 16:22 | <TabAtkins> | hsivonen: Ah, that makes sense. Cool. |
| 16:35 | jgraham | wonders who exactly the people demanding more ways to submit LC feedback expect to build the system they are demanding |
| 16:36 | jgraham | suggests that the WG would be rather happy to adopt a system they build that meets their requirements |
| 16:36 | <jgraham> | In fact it really wouldn't require anyone to adopt anything |
| 16:36 | <jgraham> | It would just exist |
| 16:37 | <jgraham> | It could be linked to from useful places of course |
| 17:24 | <beowulf> | anyone any ideas on how I could determine the zoom level (window.innerWidth/screen.width) of a webpage on a handheld device that wasn't reporting innerWidth correctly? the device is a samsung galaxy s |
| 17:29 | <bga_> | beowulf <span style="font-size: 1em">a</span> trick? |
| 17:30 | <beowulf> | bga_: will try that |
| 17:50 | <MikeSmith> | hsivonen: I'm trying to figure out what part of the validator.nu schema allows data-* attributes |
| 18:31 | <AryehGregor> | What's a good reference for using @font-face in practice, like all the gotchas you need to be aware of? People are discussing it on wikitech-l. |
| 18:33 | <miketaylr> | paul_irish has a post or two |
| 18:33 | <AryehGregor> | Ooh, Firefox 4.0 has an XSS filter that relies on a modal prompt to determine whether you can continue. :( |
| 18:34 | <AryehGregor> | "Load contents passed in the query part? The contents may contain malicious scripts. |
| 18:34 | <AryehGregor> | Continue only if you're aware that this may trigger a XSS attack and the author of this page does not take any responsibility for loading this contents" |
| 18:34 | <AryehGregor> | (I assume that's part of Firefox, dunno where else it could have come from) |
| 18:34 | <miketaylr> | http://paulirish.com/2010/font-face-gotchas/ |
| 18:34 | <Rik`> | AryehGregor: I don't think that's part of Firefox 4 |
| 18:35 | <Rik`> | AryehGregor: or maybe it's CSP in action ? |
| 18:35 | <AryehGregor> | Then where could it have come from? |
| 18:35 | AryehGregor | can't give the name of the site, since it seems like it's supposed to be private) |
| 18:35 | <AryehGregor> | s/\)$// |
| 18:35 | <Philip`> | An XSS protection script in the page itself? |
| 18:36 | Philip` | doubts Firefox would have UI with such bad grammar, or that expects users to understand what "XSS" means |
| 18:37 | <hsivonen> | MikeSmith: data-* is a pre-schema filter, IIRC |
| 18:37 | <MikeSmith> | hsivonen: ah |
| 18:37 | <AryehGregor> | It only triggered in Firefox. |
| 18:37 | <AryehGregor> | Maybe some kind of extension or something. |
| 18:37 | <Philip`> | A non-portable XSS protection script in the page itself? |
| 18:38 | <AryehGregor> | Maybe. :P |
| 18:38 | <Philip`> | NoScript? |
| 18:40 | <ako> | In IE6-8, using createStyleSheet and then setting styleElem.styleSheet.cssText to a text value that includes a @font-face declaration going into will crash IE6-8. |
| 18:40 | <ako> | sweet |
| 18:40 | <AryehGregor> | The only extension I have active is Firebug 1.7.1. |
| 18:41 | <ako> | hope they un-break ctrl+shift+c soon |
| 18:41 | MikeSmith | finds util/classes/nu/validator/xml/dataattributes/DataAttributeDroppingContentHandlerWrapper.java |
| 18:43 | <MikeSmith> | hsivonen: wondered how you did that. :) nice |
| 18:44 | <MikeSmith> | good thing there are no special restrictions on the values of data-* attributes |
| 19:08 | <AryehGregor> | Does Opera not support <wbr>? data:text/html,<!doctype html><div style="width:1em;border:1px solid black">a<wbr>b<wbr>c</div> |
| 20:29 | <TabAtkins> | What's a normal sort of resolution for a high-res image used in printing? |
| 20:29 | <TabAtkins> | (I want something reasonable for this example I'm writing.) |
| 20:34 | <zcorpan> | 300dpi? |
| 20:34 | <TabAtkins> | That's pretty much what I was thinking. kk. |
| 20:35 | <gsnedders> | 300dpi is the low end, FWIW |
| 20:37 | <Philip`> | Seems to depend somewhat on how the printer works - if it's doing colours by dithering then it probably needs higher print resolution than the original image resolution |
| 20:38 | <TabAtkins> | 300dpi works for the example, which is just to demonstrate how you can use 'image-resolution' to embed a high-res image into a page so it looks good both on-screen and in print. |
| 20:47 | <heycam> | zcorpan, it sounds like MessagePortArray should be a read only array (http://dev.w3.org/2006/webapi/WebIDL/#dfn-read-only-array) instead of a sequence, since you don't want a new object being created every time you access the property |
| 20:47 | <heycam> | zcorpan, but I'll reply on the list later this morning once I've woken up |
| 20:51 | <zcorpan> | heycam: ok |
| 20:52 | <Hixie> | didn't we already talk about that and didn't i already fix it? |
| 20:52 | <Hixie> | or was that something else that i fixed |
| 20:52 | <Hixie> | hm |
| 20:53 | <TabAtkins> | If only you had some sort of history of your revisions that you could search for this sort of thing. |
| 20:53 | <heycam> | it's quite possible MessagePortArray was the reason that bug was filed in the first place -- at least, there was something that was in html you suggested removing sequence attributes because of |
| 20:54 | <Hixie> | i think it was some microdata thing |
| 20:54 | <Hixie> | i guess i missed this one |
| 21:37 | <aho> | TabAtkins, wouldnt some CC licensed icons work? |
| 21:38 | <aho> | well, you can always just go with triangle, square, dot, circle :> |
| 21:38 | <TabAtkins> | aho: For my twitter post? Sure. But I'm just building my own right now. |
| 21:38 | <aho> | http://kaioa.com/k/test/svgsprites/index.html |
| 21:38 | <aho> | works for me ;> |
| 21:41 | <aho> | http://youtu.be/IPwCH8WQ8Qo <- webkit's input type=color thingy |
| 21:41 | <aho> | interesting that they added a color picker |
| 21:42 | <aho> | eh.. some pipette thingy |
| 21:45 | <Hixie> | ok i fixed that CORS thing from last week |
| 21:45 | <Hixie> | anything else urgent for me to work on? |
| 21:45 | <Hixie> | or should i go back to the regular pile of feedback |
| 21:46 | <Hixie> | dglazkov: yt? |
| 21:46 | <dglazkov> | Hixie: I certainly am |
| 21:46 | <Hixie> | dglazkov: re the scoped thing, keep in mind that there's more to scoping <style> than just scoping the selectors. For example, @font-face rules have to not leak to the outer scope. |
| 21:47 | <Hixie> | dglazkov: otherwise, someone who is syndicating content that gets scoped elsewhere could screw around with the font of the whole page |
| 21:47 | <dglazkov> | Hixie: oh. where do I read about this? |
| 21:47 | <Hixie> | dglazkov: "For scoped CSS resources, the effect of @-rules must be scoped to the scoped sheet and its subresources, even if the @-rule in question would ordinarily apply to all style sheets that affect the Document. Any '@page' rules in scoped CSS resources must be ignored." |
| 21:47 | <zcorpan> | Hixie: there were some bugs about cross-origin |
| 21:48 | <Hixie> | dglazkov: http://www.whatwg.org/specs/web-apps/current-work/complete.html#attr-style-scoped |
| 21:48 | <Hixie> | zcorpan: ah, let me check those out |
| 21:48 | <dglazkov> | Hixie: awesome |
| 21:48 | <dglazkov> | throw it on the bug |
| 21:48 | <Hixie> | dglazkov: i deleted the bugmail, do you recall the number? |
| 21:49 | <dglazkov> | Hixie: https://bugs.webkit.org/show_bug.cgi?id=49142 |
| 21:50 | <Ms2ger> | Hixie, http://www.w3.org/Bugs/Public/show_bug.cgi?id=12724 maybe? :) |
| 21:56 | <Hixie> | Ms2ger: that is like the _definition_ of not urgent. :-P |
| 21:56 | <Ms2ger> | :) |
| 21:59 | Hixie | comments in the other bug to suggest it be changed to be the other way around |
| 22:02 | <zcorpan> | everyone, bring paint for the bikeshed http://www.w3.org/Bugs/Public/show_bug.cgi?id=12679 |
| 22:03 | <Hixie> | :-) |
| 22:03 | <Hixie> | zcorpan: i only found three bugs including that one |
| 22:04 | <Hixie> | zcorpan: let me know if i missed any |
| 22:04 | <Philip`> | Surely it should be "xorigin" |
| 22:04 | <Hixie> | you're supposed to put the paint on the shed, not sniff it |
| 22:05 | <zcorpan> | Philip`: not xdomain? |
| 22:05 | <TabAtkins> | ×origin |
| 22:05 | <TabAtkins> | We should embrace unicode! |
| 22:05 | <zewt> | nandigin |
| 22:05 | <Hixie> | maybe xoxoxo="" would make the spec more approachable to teen girls? |
| 22:05 | <TabAtkins> | ✝origin |
| 22:06 | <Hixie> | has to be ascii |
| 22:06 | <TabAtkins> | Bah. |
| 22:06 | <Philip`> | "xs", as in XSS |
| 22:09 | <Philip`> | zcorpan: Consistency with XDomainRequest is a good argument in favour of that |
| 22:09 | <zcorpan> | Hixie: iirc jgraham made the case that http-equiv and accept-charset are legacy and data-* and aria-* use hyphen because they are different to "normal" attributes |
| 22:10 | <Hixie> | cross-origin: tomorrow's legacy, today! |
| 22:12 | <zcorpan> | Hixie: people will go "why did Hixie not use a hyphen in formnovalidate but used a hyphen in cross-origin?" |
| 22:12 | <Hixie> | dude, HTML's attributes have every manner of quirks and idiosyncracies |
| 22:13 | <zcorpan> | so? |
| 22:13 | <Hixie> | anyone looking for logic in the naming scheme there has already embarked on a fool's errand long before i come along |
| 22:14 | <Hixie> | (you're going to win this argument, i'm just stalling for time because i'm editing another e-mail at the moment) |
| 22:15 | <TabAtkins> | Well, I went ahead and pushed zcorpan's argument into the bug, so you can agree with it there. ^_^ |
| 22:15 | <zcorpan> | heh |
| 22:24 | <gsnedders> | Hixie: (you know how to win arguments and write emails quickly, I see) |
| 22:25 | <Hixie> | hm? |
| 22:35 | <zcorpan> | Hixie: the dfn bug is a result of id renaming and putting id on span/dfn in the heading |
| 22:35 | <zcorpan> | Hixie: which also makes the status box misaligned in http://www.whatwg.org/specs/web-apps/current-work/complete/the-iframe-element.html#the-video-element |
| 22:36 | <Hixie> | ah |
| 22:36 | <Hixie> | bummer |
| 22:36 | <Hixie> | any suggestions on how to fix it? |
| 22:36 | <Hixie> | i could tweak the database i guess |
| 22:36 | <zcorpan> | ...that's what i was going to suggest :) |
| 22:36 | <Hixie> | that's a pain |
| 22:36 | <Hixie> | wanna do it? :-) |
| 22:37 | <zcorpan> | no :) |
| 22:37 | <Hixie> | anyone else want to poke at the mysql database behind the status boxes? :-) |
| 22:37 | <zcorpan> | you could implement UI to change the id for the boxes |
| 22:37 | <zcorpan> | if that's less painful |
| 22:37 | <Hixie> | yeah i'll get right on that as soon as i've finished dealing with this feedback |
| 22:38 | <Hixie> | only 1931 e-mails left |
| 22:38 | <zcorpan> | okie dokie |
| 22:38 | <Hixie> | (if anyone does want to fix this let me know and i'll send you the username/password to the mysql box) |
| 22:40 | zcorpan | adds crossorigin to html-elements |
| 22:41 | <Hixie> | ifette: is websockets ready for the api update? |
| 22:45 | <AryehGregor> | Oh, it looks like insertparagraph is meant to be basically the same as hitting Enter. Interesting. |
| 22:45 | <AryehGregor> | So I can spec that easily now, at least for non-Gecko. |
| 22:47 | <zcorpan> | AryehGregor: makes sense (re formatblock) |
| 22:51 | <zcorpan> | AryehGregor: what if you start with <body contenteditable></body> and do insertparagraph? opera gives two <p>s, ie and firefox just one, iirc |
| 22:51 | <AryehGregor> | zcorpan, Firefox treats insertparagraph like formatBlock with argument "p", so it's not comparable. |
| 22:52 | <AryehGregor> | Interesting corner case. I'd like to say it's the same as hitting Enter in all cases, which suggests two. |
| 22:53 | <TabAtkins> | Argh, Chrome's formatting of SVG-in-<img> is SO BROKEN. |
| 22:53 | <zcorpan> | AryehGregor: agree it would make sense |
| 22:53 | <AryehGregor> | TabAtkins, so standardize it! |
| 22:53 | <TabAtkins> | AryehGregor: It is. We're just broken. |
| 22:53 | <AryehGregor> | Where is it standardized? |
| 22:54 | <TabAtkins> | The Image Values spec. |
| 22:55 | <zcorpan> | it's a DRAFT |
| 22:55 | <zcorpan> | it's NON-NORMATIVE |
| 22:55 | <TabAtkins> | omg |
| 22:55 | <TabAtkins> | YOU'RE RIGHT |
| 22:55 | <zcorpan> | it's NOT A STANDARD |
| 22:56 | <smaug____> | what is a standard nowadays ;) |
| 22:56 | <zcorpan> | html 4.01 and css 2.0 |
| 22:56 | <AryehGregor> | Image Values as in CSS Image Values, or some other Image Values? |
| 22:56 | <TabAtkins> | The former. |
| 22:57 | <TabAtkins> | Theoretically, <img>s handle sizing concerns with the same mechanisms that background images use. |
| 22:57 | <zcorpan> | (some peeps at sitepoint forums actually argue along those lines) |
| 22:58 | <abarth> | TabAtkins: SVG-in-IMG is a disaster |
| 22:58 | <abarth> | TabAtkins: blame eseidel |
| 22:58 | <TabAtkins> | abarth: I WILL |
| 22:58 | <abarth> | it's a giant hack and should be deleted, IMHO |
| 22:58 | <TabAtkins> | I'm going to have to make a PNG of this SVG now just so I don't have retarded sizing issues. |
| 22:58 | <abarth> | why not just use SVG-in-HTML ? |
| 22:59 | <abarth> | it makes infinitely more sense |
| 22:59 | <TabAtkins> | Because that won't validate as HTML4, which CSS specs are required to be. >_< |
| 22:59 | <AryehGregor> | Oh, you're only worried about sizing? |
| 22:59 | <abarth> | sounds like a bug in the CSS specs |
| 22:59 | <TabAtkins> | Well, it's a bug in w3c process. |
| 22:59 | <AryehGregor> | I thought you were talking about more important stuff, like how dynamic content is treated. |
| 22:59 | <abarth> | TabAtkins: use XHTML :) |
| 22:59 | <TabAtkins> | AryehGregor: Yes. SVG images without explicit viewport sizes are automatically treated as if their viewport was the size of the screen. |
| 23:00 | <zcorpan> | TabAtkins: if you would have just followed the STANDARDS then you wouldn't be having these issues |
| 23:00 | <TabAtkins> | Rather than the size of the <img>, as would make some kind of sense. |
| 23:00 | <AryehGregor> | TabAtkins, why don't you give an explicit viewport size? |
| 23:00 | <TabAtkins> | AryehGregor: Because I gave it a viewBox, which *should* be enough, and I'm angry at it. |
| 23:02 | <TabAtkins> | But anyway, I've now given it an explicit width and height instead, grr. |
| 23:44 | <kangax> | Can someone clarify canvas' "destination-atop" globalCompositeOperation? Chrome and FF disagree (based on spec, it seems like Chrome is right). |
| 23:45 | <kangax> | test: http://kangax.github.com/jstests/canvas_globalcompositeoperation_test/ — choosing destination-atop and oval.png "clips" destination content in Chrome, but not in FF. Which one is right? |
| 23:47 | <roc> | FF |
| 23:47 | <roc> | try it in IE9 |
| 23:47 | <roc> | or opera |
| 23:47 | <kangax> | i did |
| 23:47 | <kangax> | all non-webkit's seem to agree |
| 23:48 | <roc> | yes, it's a Webkit bug |
| 23:49 | <roc> | they clip the effect of the operator to the shape of the source object, or something like that |
| 23:49 | <roc> | the spec says not to do that |
| 23:49 | <TabAtkins> | Yeah, that's basically it. For some defintion of "the shape". |
| 23:49 | <kangax> | webkit's behavior looks more useful for my use case |
| 23:49 | <roc> | kangax: maybe so, but you can probably clip to the shape yourself easily enough |
| 23:49 | <Philip`> | Is your use case unable to use clip()? |
| 23:49 | <kangax> | i basically want to clip all the content to my (masking) image |
| 23:49 | <roc> | I don't think Webkit's behavior is bad, but no-one could ever figure out how to spec it right |
| 23:49 | <erlehmann> | kangax, does this help? https://developer.mozilla.org/en/Canvas_tutorial/Compositing |
| 23:50 | <kangax> | that's the thing — clip operates on current path, from what i understand, but I'd like to use an image (which doesn't affect it) |
| 23:50 | <roc> | just clip to the rectangle of the image |
| 23:51 | <kangax> | let's say i have an image of a flower — just a contour really — and i want to clip all the content to it. I don't have vector representation of an image. How to do it? |
| 23:52 | <roc> | the Webkit bug doesn't help you there does it? My understanding is that the "shape" it clips to would be the image rectangle in that case |
| 23:53 | <kangax> | ah yes, that's the thing |
| 23:53 | <kangax> | clipping to non-rectangular shape is what's useful |
| 23:53 | <TabAtkins> | The SVG compositing spec has a switch for the two behaviors. |
| 23:53 | <TabAtkins> | Of course, SVG has a good definition of the "shape" of an object. ^_^ |
| 23:53 | <kangax> | in which case I'd be able to create an image with transparent bg |
| 23:54 | <kangax> | ..and clip everything to that image |
| 23:55 | <kangax> | TabAtkins: perhaps introducing another compositing mode would make sense then? i would think my usecase is not that uncommon |
| 23:55 | <Philip`> | The spec composites the image as if it were infinitely large and surrounded by transparency, so if you want everything outside the image to be clipped out then you should make the image contain transparency for clipped-out regions |
| 23:56 | <Philip`> | and then probably render with destination-in so it shows the original canvas content where the image is solid, and shows transparency elsewhere |
| 23:56 | <Philip`> | if that's roughly what you want |
| 23:56 | <kangax> | Philip`: but my overlaying (source) image is exactly like this — has content in the middle and transparency surrounding it |
| 23:57 | <kangax> | i though this opaque content in the middle will serve as clipping mask |
| 23:57 | <kangax> | *thought |
| 23:57 | <Philip`> | Can't you just use destination-in (I think), then? |
| 23:58 | <kangax> | that doesn't work in either Chrome nor FF |
| 23:59 | <kangax> | ..neither in Opera (just checked — all of them result in white nothingness) |