2011 Nov 24, 7:45
From the document: ‘Appendix B. Implementation Report: The encoding defined in this document currently is used for two different HTTP header fields: “Content-Disposition”, defined in [RFC6266],
and “Link”, defined in [RFC5988]. As the encoding is a profile/clarification of the one defined in [RFC2231] in 1997, many user agents already supported it for use in “Content-Disposition” when
[RFC5987] got published.
Since the publication of [RFC5987], two more popular desktop user agents have added support for this encoding; see http://purl.org/
NET/http/content-disposition-tests#encoding-2231-char for details. At this time, only one major
desktop user agent (Safari) does not support it.
Note that the implementation in Internet Explorer 9 does not support the ISO-8859-1 encoding; this document revision acknowledges that UTF-8 is sufficient for expressing all code points, and
removes the requirement to support ISO-8859-1.’
Yay for UTF-8!
technical http http-headers ie9 internationalization utf-8 encoding 2011 Nov 21, 11:00
A bug came up the other day involving markup containing <input type="image" src="http://example.com/...
. I knew that "image" was a valid input type but it wasn't until that moment
that I realized I didn't know what it did. Looking it up I found that it displays the specified image and when the user clicks on the image, the form is submitted with an additional two name
value pairs: the x and y positions of the point at which the user clicked the image.
Take for example the following HTML:
<form action="http://example.com/">
<input type="image" name="foo" src="http://deletethis.net/dave/images/davebefore.jpg">
</form>
If the user
clicks on the image, the browser will submit the form with a URI like the following:
http://example.com/?foo.x=145&foo.y=124
.
This seemed like an incredibly specific feature to be built directly into the language when this could instead be done with javascript. I looked a bit further and saw that its been in HTML since
at least HTML2, which of course makes much more sense. Javascript barely existed at that point and sending off the user's click
location in a form may have been the only way to do something interesting with that action.
uri technical form history html 2011 Nov 17, 11:00
I had previously replaced my use of Delicious with Google Reader. Delicious had a number of issues during their switch over from Yahoo to the new owners and I was eventually fed up enough to
remove it from daily use. I used Delicious to do the following things:
- Create a list of things to read later
- Save things to read again in the future
- Search through things I read and enjoyed (esp via tags)
- Annotate and share things on my blog
I realized that since I did most of my web browsing in Google Reader now anyway I may as well make use of its features. I star things to note I want to read it later or save to read again
later. I can annotate with notes in Google Reader and I can share items to my web site by way of the shared items feed. Additionally for when I'm not in Google Reader there's a bookmarklet to add
an arbitrary web site as a shared item in Google Reader.
Of course I wrote this and switched over about 1 week before Google removed the sharing feature from Google Reader. I'm irritated but in practice it forced me to find a different option which has
worked out mostly better. New blog post coming soon about that...
blog delicious me technical google-reader google feed 2011 Nov 17, 12:58 2011 Nov 14, 7:51
Includes ‘511 Network Authentication Required’ for airport/hotel/coffee shop scenarios! Am I too excited about this?
technical ietf http http-status-codes 2011 Nov 14, 12:34
I wrote my HTML against IE9 and continually validated with Chrome as I went. Afterward I tried it in FireFox and found out that FireFox has textContent whereas IE9 & Chrome have innerText
technical web web-browser firefox ie9 chrome ie innertext textcontent js html 2011 Oct 25, 5:37
An original iPod guy has a new company that makes... wait for it... thermostats. Weird. Well they look cool anyway.
technical 2011 Oct 24, 2:14
Ninjas fight dirty.
technical 2011 Oct 20, 6:52
Wow, FTA: "Given all of this, reporter Charlie Savage of the NY Times filed a Freedom of Information Act request to find out the federal government's interpretation of its own law... and had it
refused. According to the federal government, its own interpretation of the law is classified."
technical 2011 Sep 23, 10:13Post technical 2011 Sep 20, 9:27Interview with someone who bought the limited edition Back to the Future shoes: "[Interviewer] Have you watched the Back to the Future movies? [Respondent] Yeah, some of em. The hoverboards and shit.
That was cool." ARGH! Not worthy!
humor bttf nike shoes 2011 Sep 20, 7:17There's no race between posting to a web worker and the web worker setting up its message handler as long as the web worker sets its message handler in the first sync. block of code that runs in the
web worker: "Basically, once the initial worker script returns, the worker's port is enabled and the normal message port event delivery mechanism kicks in (including dropping unhandled messages on
the floor)."
technical web-worker webbrowser programming postMessage 2011 Sep 19, 12:53Counter intuitive argument for not making the larger fix: "Should we fix them all preemptively, meaning the next time they block us it will be through some more complex mechanism that's harder to
figure out? Or should we leave things as they are, knowing there will be more blocking events but also knowing that we can solve them easily?"
tor censorship government iran technical 2011 Aug 31, 10:03Awesome shirt of Tesla/Edison in the style of the AC/DC logo.
science humor electricity tesla edison tshirt shirt wishlist 2011 Jul 27, 10:33The write-progress command in powershell allows scripts to express their progress in terms of percent or time left and powershell displays this in a friendly manner at the top of my window.
Surprisingly, not hooked up to the Shell's TaskbarItemInfo's progress.
technical powershell progress coding shell 2011 Jul 10, 5:49"The ‘analog dollars to digital dimes’ problem doesn’t actually seem to be a problem. It seems to be a feature of reality. Digital revenue per head is not replacing lost print revenue and, barring
some astonishment in the advertising market, it never will."
news media journalism clay-shirky