Comment by makmanalp

16 years ago

This is really odd, I'm having a bug on chrome windows where the html gets printed out as plaintext. MIME type issues on the server side maybe? Other than that, looks like an interesting read.

9 comments

makmanalp

Reply
tlrobinson  16 years ago

Yeah...

   Content-Type: text/plain; charset=ISO-8859-1

Interesting that Safari is "smart" and ignores the content type in this case.

  • philwelch  16 years ago

    My Safari printed the raw HTML source at first, but rendered the HTML upon reload.

    • watmough  16 years ago

      Yeah, mine too. I'm almost motivated to go look why... but not quite.

      I looked for a 'View as' menu item prior to reloading, but very interesting that a reload fixed it.

  • makmanalp  16 years ago

    Another interesting thing is exploring being pedantically standards compliant (breaking usefulness sometimes) versus bending standards (in the expense of encouraging bad practice)

    • tlrobinson  16 years ago

      Good old Postel's Law.

      If all browsers actually paid attention to Content-Type then this site probably would have fixed the actual problem. Instead we have a world where it works in only some browsers, and naïve users consider the one that is technically more correct to be "broken".

      1 reply →