What's the browser reality of HTTP content-nego via Accept? What do IE/FF/WebKit ask for when resolving <img src=""> ?
-
-
Replying to @clemensv
@clemensv@kellabyte you might find https://developer.mozilla.org/en-US/docs/HTTP/Content_negotiation … enlightening. it answers your question specifically1 reply 1 retweet 0 likes -
Replying to @steveklabnik
@steveklabnik@kellabyte Thank you for that link. if WebKit doesn't do it right, it seems pointless to rely on that.1 reply 0 retweets 0 likes -
Replying to @clemensv
@clemensv@kellabyte what do you mean by ‘do it right?’1 reply 0 retweets 0 likes -
Replying to @steveklabnik
@steveklabnik@kellabyte Giving explicitly preference for image/* types on <img> would be 'doing it right'. Seems FF and IE9 are doing that.3 replies 0 retweets 0 likes -
Replying to @clemensv
@clemensv@kellabyte I don’t know about the details of your situation, though2 replies 0 retweets 0 likes -
Replying to @steveklabnik
@steveklabnik@kellabyte if a browser is giving */* out of a context where it's clearly only willing to render image content that's a bug1 reply 0 retweets 0 likes -
Replying to @clemensv
@clemensv@kellabyte … I can see that perspective. I think they’re probably just trying to adhere to Postel’s Law.1 reply 0 retweets 0 likes -
Replying to @steveklabnik
@steveklabnik@kellabyte That would be to clearly declare what you're willing to take but then be lenient if you get something else1 reply 0 retweets 0 likes
@clemensv @kellabyte heh, yeah. Too many plane rides today. :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.