| 17:27 | <annevk> | So I guess I should document the various Fetch policies we have to illustrate we lack logic |
| 17:37 | <conspiritech__> | is there any one or two line html or css way for me to display a 'no svg support' error for an image but have it not be read by screen reader? |
| 17:41 | <conspiritech__> | like an alt text except that only sighted users see it would be ideal |
| 17:46 | <annevk> | Are there still user agents without SVG support? |
| 17:46 | <conspiritech__> | IE8 |
| 17:47 | <conspiritech__> | and anyone with compatibility mode on accidentally such as my dad |
| 17:47 | <annevk> | I think Firefox might have some proprietary way to do that. |
| 17:47 | <annevk> | The requirement that a screen reader does not see it makes a standardized way hard given the constrain of HTML/CSS |
| 17:48 | <conspiritech__> | i only have one sag, but i imagine if they were suddenly beset by dozens of svg alt text error messages they wouldn't be happy |
| 17:49 | <annevk> | you could do <object data=svg><img src=svgnotsupportedmessage></object> maybe |
| 17:50 | <conspiritech__> | around this " <div><img id="topimg" src="images/logo3.svg" alt="logo company name" /></div> |
| 17:50 | <conspiritech__> | where does that go? |
| 17:54 | <conspiritech__> | oh i think i see |
| 17:55 | <conspiritech__> | just after or something |
| 17:55 | <conspiritech__> | never heard of <object> before |
| 17:56 | <conspiritech__> | thanks |
| 18:13 | <annevk> | yw |
| 18:14 | <conspiritech> | did not work the way I tried it. but I've spent too much time on it |
| 19:03 | <annevk> | http://wiki.whatwg.org/wiki/HTTP_Fetch_Policy is what I have thus far |
| 20:22 | <odinho> | Oh FSF found out about EME -- http://www.defectivebydesign.org/no-drm-in-html5 |
| 22:05 | <Hixie> | asmodai: yeah, i didn't mean to say you were missing the point :-) |
| 22:05 | <Hixie> | MikeSmith: ah, yeah, transparent could be the issue... |
| 22:05 | <Hixie> | MikeSmith: no idea how to make that better :-( |
| 22:38 | <MikeSmith> | Hixie: me neither |
| 22:39 | <MikeSmith> | dude just needs to follow the "transparent" link |
| 22:43 | <asmodai> | Hixie: Didn't take your sentence as such :) |
| 22:43 | <asmodai> | So no worries ^^ |
| 23:21 | <ari-_-e> | so here's a conundrum for you: |
| 23:21 | <ari-_-e> | I add an iframe to my page which has a different origin than my page |
| 23:22 | <ari-_-e> | when that iframe gets loaded, it actually gets redirected to something else that is not the same origin as it originally was |
| 23:22 | <ari-_-e> | now I want to postMessage to the window in that iframe |
| 23:22 | <ari-_-e> | what targetOrigin do I use? |
| 23:29 | <ari-_-e> | let's say that the redirect only changed the protocol from http to https |
| 23:29 | <ari-_-e> | so it's still basically the same page and it still makes sense to send the message |