<img data-web="2.0">



  • Red Thread Games has recently cashed in on their rather successful Dreamfall Chapters Kickstarter.
    To celebrate, they put together a fan-art competition. I can find the nominees here. Except I can't, because none of the thumbnails will load.

    Upon further investigation, it appears that they are using the finest Web 2.0 technology to display their thumbnails. Behold, the glorious img 2.0 tag:


    <img data-image-id="513e69e9e4b079292073f6ea"
    alt="bBVbgTm.jpg"
    data-image-focal-point="0.49473684210526314,0.17098445595854922"
    data-image-dimensions="1040x2087"
    data-src="http://static.squarespace.com/static/5056eb0de4b0ddb0f538eaf8/513e69d5e4b0170b1869a4e4/513e69e9e4b079292073f6ea/1363044846079/bBVbgTm.jpg"
    data-image="http://static.squarespace.com/static/5056eb0de4b0ddb0f538eaf8/513e69d5e4b0170b1869a4e4/513e69e9e4b079292073f6ea/1363044846079/bBVbgTm.jpg"
    data-load="false">

    And the reason the snazzy javascript failed to turn the image into an image that also happens to work? I installed firebug to find this in the console:

    Image corrupt or truncated: http://static.squarespace.com/static/5056eb0de4b0ddb0f538eaf8/t/512a90d4e4b03f854eec77e0/1361744084667/9.jpg

    Normally I can tell you my ISP is shitty without installing firebug first though.



  • So your complaint is that their perfectly-functional website doesn't work because YOUR ISP corrupts their files? Or am I confused?



  • They're doing it so that they can have asynchronous image loading. It looks like they might also be doing it so they can load optimized image sizes for mobile devices.

    In short, the page requires javascript (not uncommon) and broke because your ISP sucks. The image in question would display as en error even if they didn't use javascript.



  • @dynedain said:

    They're doing it so that they can have asynchronous image loading.

    Really? Because I'm pretty sure browsers have been doing asynchronous loading on their own since about 1998. Also, having an image display as an error would actually be preferable to the page pretending the image never existed.



  • @Faxmachinen said:

    @dynedain said:
    They're doing it so that they can have asynchronous image loading.

    Really? Because I'm pretty sure browsers have been doing asynchronous loading on their own since about 1998. Also, having an image display as an error would actually be preferable to the page pretending the image never existed.

    Let me rephrase that.... asynchronous loading where you know the image is loading after dom structure is complete. Normally this is used to display a loading graphic until an image is ready for display.



  •  It took me a while to figure out how to come to the thread and say this:

    Thanks for breaking gmail, you drape-fucker:




  • @Lorne Kates said:

     It took me a while to figure out how to come to the thread and say this:

    Thanks for breaking gmail, you drape-fucker:


    Community Server doesn't sanitize post titles in emails? Quick! Nobody abuse that to make CS email everyone a script that no sane email client executes!



  • @Lorne Kates said:

    Thanks for breaking gmail, you drape-fucker:

    That's a problem with gmail, not - for once - CS. It's interpreting the subject as literal HTML rather than escaping the characters - the title bar of your browser should show the subject.



  • @PJH said:

    It's interpreting the subject as literal HTML rather than escaping the characters

    Because it's in the body of the message and not the subject, because CS is shit?



  • TDWTF Forums - Automated Email

    TDWTF Forums - Automated Email



  • <h1><img src="http://i.imgur.com/A5WtQcT.gif"> <blink><span style="color: red">I wonder if this works?</span></blink></h1>

    oh come on i have to type a message?



  •  Jesus fucking christ, GMAIL. This is 2013. What the fuck are you doing accepting HTML tags in mail subject?!? I'd expect this shit from Hotmail. But-- come on!




  • The subject is above the text TDWTF Forums - Automated Email. Below the name of the sender is the body of the email, which includes the title of the post for some reason.



  • @Lorne Kates said:

    GMAIL... What the fuck are you doing accepting HTML tags in mail subject?!?
     

    Accepting them isn't the problem (it's just text after all) - displaying them unescaped is.

    Have you checked the raw source of that message? It looks like the subject is being displayed escaped. Is that HTML actually the body of the next message ,or have they repeated the header and not sanitised it this time around?



  • Re: <h1><img src="http://eternallybored.org/tdwtf/lineargradient.png"> <blink><span style="color:red;text-decoration:blink">I wonder if this works?</span></blink></h1>

    @Cassidy said:

    Have you checked the raw source of that message? It looks like the subject is being displayed escaped. Is that HTML actually the body of the next message ,or have they repeated the header and not sanitised it this time around?
    GMail seems fine - CommunityServer is the one that the message title unescaped in the post body.



  • @ender said:

    GMail seems fine - CommunityServer is the one that the message title unescaped in the post body.
     

    Is it? I don't see it interpreted on the forums. I thought that screenshot was from GMail, not from CS.

    However, perfectly happy to concede the point. It don't affect meh, I don't use GMail, I see the forums as intended.

    i.e.: busted.



  • @Cassidy said:

    Is it? I don't see it interpreted on the forums. I thought that screenshot was from GMail, not from CS.
    It's only unescaped in the body of e-mails that are sent out.



  • Re: <h1 style="positionabsolute;top:0px;left:0px;"><img src="http://eternallybored.org/tdwtf/lineargradient.png"> <blink><span style="color:red;text-decoration:blink">I wonder if this works?</span&gt

    @ender said:

    @Cassidy said:
    Is it? I don't see it interpreted on the forums. I thought that screenshot was from GMail, not from CS.
    It's only unescaped in the body of e-mails that are sent out.
     

    The screenshot is from Gmail. It is interpreting the Subject line as HTML and rendering-- breaking the subject line.



  • Re: <h1 style="float:left;"><img src="http://eternallybored.org/tdwtf/lineargradient.png"> <blink><span style="color:red;text-decoration:blink">I wonder if this works?</span&gt

     Interesting: CS strips out the semi-colon after position:

    Let's see if gmail breaks on "float:left"



  •  @Lorne Kates said:

     Interesting: CS strips out the semi-colon after position

    Let's see if gmail breaks on "float:left"

     Goddamn it Gmail:

     

     



  • <b style="font:100pt comic sans ms">THIS IS FUN</b>

    @Lorne Kates said:

    @ender said:

    @Cassidy said:
    Is it? I don't see it interpreted on the forums. I thought that screenshot was from GMail, not from CS.
    It's only unescaped in the body of e-mails that are sent out.
     

    The screenshot is from Gmail. It is interpreting the Subject line as HTML and rendering-- breaking the subject line.


    The subject line is at the top, and properly escaped. CS includes the title in the body of the email, which gmail - apart from sanitizing it - has no reason to change at all.



  • Sorry? What's the WTF here? That if you send GMail a HTML email it'll render it? I don't get what the "goddamn it" is about.

    EDIT: Oh is this thread seriously about the concept "Community Server includes another copy of the post subject in the BODY of the email" that's been explained in this thread like 4 times and idiots still aren't getting? Christ.


  • Winner of the 2016 Presidential Election

    <audio autoplay loop><source src="http://users.content.ytmnd.com/2/b/e/2bec208f4a8ba47e051021e9cd59b6f2.wav" type="audio/wav"></audio>

    How about this?



  • @blakeyrat said:

    Sorry? What's the WTF here? That if you send GMail a HTML email it'll render it?
     

    It's that it renders the HTML inside the Subject Line.

     @blakeyrat said:

    Sorry? What's the WTF here? That if you send GMail a HTML email it'll render it? I don't get what the "goddamn it" is about.

    EDIT: Oh is this thread seriously about the concept "Community Server includes another copy of the post subject in the BODY of the email" that's been explained in this thread like 4 times and idiots still aren't getting? Christ.

    So it's a twoforone WTF. Aweseome.

     




  •  @joe.edwards said:

    <audio autoplay loop><source src="http://users.content.ytmnd.com/2/b/e/2bec208f4a8ba47e051021e9cd59b6f2.wav" type="audio/wav"></audio>

    How about this?

    Thank goodness no!



  • @Lorne Kates said:

    It's that it renders the HTML inside the Subject Line.



    Gmail does NOT render HTML inside the subject line.

    You can see the "conversation subject line" - usually title of first or most recent email - in plain black letters at the top of your screenshot.

    Each mail's subject is hidden by default, until you click the small drop-down icon near the "TDWTF Forums to me" header at top of a mail. If you expand that, you'll see it escaped there too.

    Community Server puts the post title in the email subject and then again in the email body, which is HTML.

    Community Server does not htmlescape the post title when it puts it in the email body. (Hint: That's TRWTF.)

    Gmail renders the email body as HTML because it is sent as HTML. There's no way for Gmail to know that this particular chunk of HTML in beginning of the body came from the post title.

    ...

    ... I've got trolled, didn't I?



  • @bannedfromcoding said:

    @Lorne Kates said:
    It's that it renders the HTML inside the Subject Line.



    Gmail does NOT render HTML inside the subject line.

    You can see the "conversation subject line" - usually title of first or most recent email - in plain black letters at the top of your screenshot.

    Each mail's subject is hidden by default, until you click the small drop-down icon near the "TDWTF Forums to me" header at top of a mail. If you expand that, you'll see it escaped there too.

    Community Server puts the post title in the email subject and then again in the email body, which is HTML.

    Community Server does not htmlescape the post title when it puts it in the email body. (Hint: That's TRWTF.)

    Gmail renders the email body as HTML because it is sent as HTML. There's no way for Gmail to know that this particular chunk of HTML in beginning of the body came from the post title.

    ...

    ... I've got trolled, didn't I?

    I... unfortunately... don't think so. This thread is full of ITiots.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.