[JoshTriplett]

I typed in "example.org", and got back "Please enter a URL". For convenience, consider automatically assuming "http:// in the front if the user doesn't specify a URL scheme. (Please do continue allowing URLs with http:// or https:// explicitly specified, though.) You shouldn't make that assumption if you provide an API in the future (API callers should specify full valid URLs), but it would make the current web interface more friendly.

Whatever renderer you used to render the page has absolutely no antialiasing in its font rendering, resulting in pixelated rendering.

[hashbo]

Josh that’s really interesting, what browser were you using, because the app doesn’t say ‘Please enter a URL’ this must be a browser feature working against input type=‘url’. I’d love to know the browser you were using. It certainly shouldn’t require a http:// at the front.

Yeah you’re 100% right about the fonts, I definitely plan to sort that out ASAP.

[JoshTriplett]

Oh, interesting! I use Firefox 10, and I didn't realize that that validation came from the browser rather than your page.

[hashbo]

Josh if you see it still let me know. I just hacked a quick JS fix and tested in FF10 and all seems to be well. But as you know each version of each browser has it’s own little features :-)

[JoshTriplett]

Seems to work now. Thanks!

[andygcook]

The "Please enter a URL" prompt also happens in Chrome (version 16.0.912.77)

[thealoof]

+1 for the anti-aliasing

[hashbo]

Added, and extra fonts and colour depth fixed :-)