Tab Completion

I'm Tab Atkins Jr, and I wear many hats. I work for Google on the Chrome browser as a Web Standards Hacker. I'm also a member of the CSS Working Group, and am either a member or contributor to several other working groups in the W3C. You can contact me here.
Listing of All Posts

Comments!

Last updated:

The day has finally arrived! I added comments to the site. I expect I'll tweak them a lot over the next few weeks, but feel free to go crazy on them for now.

If you want to post a test comment, do so on this post.

Commenting Policy

I will delete the fuck out of your comments if you're trolling, spamming, or just plain vacuous, at my own discretion. If you don't have something worthwhile to add, don't post.

Markdown Syntax

I currently support most of Markdown in the comments. You can check the progress of the comment parser at my markdown github repo.

You can use all of the block-level elements except headings.

You can use all of the inline-level elements, including reference-style links.

(a limited set of Markdown is supported)

Few comments about your comment system (in fact, this is my own todo/check list for the comment system, even if some items are already done):

  • Does it retain my credentials (cookie/localStorage) so that I don't have to type them every time?
  • Does it send you a mail when a new comment is added on your blog (you don't want to miss comments, do you)? Does it support guest subscription on a blog post?
  • Do you have a easy way to delete/modify comments out of order, if something go wrong (spam)?
  • If you support comment subscription, there should be a link in the mails to allow people to unsubscribe.
  • Does it support all unicode glyphs like ♥ and ∫sin(x).dx ? Is it <a href="about:invalid">secure?
  • Yay, I really liiiiike it :-) I hope to make more useful comments to your wonderful blog posts soon!
Reply?

(a limited set of Markdown is supported)

Oh, I know it's stupid but I like

textarea {
    overflow-y: auto;
}

(btw, this is a test for preserving whitespace)

Reply?

(a limited set of Markdown is supported)

Hurp durp, can't believe I forget to add white-space:pre-wrap; to the rules.

Reply?

(a limited set of Markdown is supported)

All right, credential-saving now works, woo! Uses localStorage, very trivial.

I think for comment subscription, I'll provide comment rss feeds. Easier for me, as I don't have to screw around with remembering people's emails and preferences.

I can easily delete/modify comments - I just pull down the appropriate file from FTP, modify it, and put it back up again. ^_^

Reply?

(a limited set of Markdown is supported)

Yay!

  1. Comment permalink is wrong, they miss the “b” in first “b4K90”, so now they give 403.
  2. While the width of the blog is fluid, the width of comments is not, so adding some max-width (with some other minor fixes to take care of paddings) would be great.
  3. It would be nice to add something more than simple space between the comment number and the date, right now it's a bit hard to read.
Reply?

(a limited set of Markdown is supported)

  1. And it would be nice to send user to the comment's permalink after he posts his comment, so he would be sure that everything went well.
Reply?

(a limited set of Markdown is supported)

Thanks for the suggestions, Roman! Fixed all of them, but there's still some fluidity issues with the blog header. I need to pull out a MQ to switch the header to be vertical when it gets too small.

Reply?

(a limited set of Markdown is supported)

Thank you for adding comments.

I find it's too hard to read the first couple of lines of linked-to comments, over the black end of the gradient. (In Firefox. Possibly the gradient gradients differently in other browsers.)

Reply?

(a limited set of Markdown is supported)

Ah, more specifically, the ‘black text on almost-black gradient’ problem only occurs on long comments, because the gradient is stretched over the height of the comment, so the black part goes down farther than on short ones.

See comment #6 above for an example.

Reply?

(a limited set of Markdown is supported)

Re #15:

That's... not what they're supposed to look like. It appears that FF is dropping the background declaration that should be setting that gradient to a 2px stripe along the right side. I wonder why?

Reply?

(a limited set of Markdown is supported)

Re #17: Hmmm, I get the same behaviour as Firefox in Chromium 18 (WebKit 535.19). I see the intended behaviour — which looks really nice, by the way — in Chrome 21 (WebKit 537.1).

Nothing special about those versions: they just happen to be the two WebKit-based browsers I have installed. But perhaps if you can spot the difference between those, it'll give a clue to the Firefox behaviour too.

Reply?

(a limited set of Markdown is supported)

Re #18:

Your comment system dropped my first paragraph. The fully comment was:

Hmmm, I get the same behaviour as Firefox in Chromium 18 (WebKit 535.19). I see the intended behaviour — which looks really nice, by the way — in Chrome 21 (WebKit 537.1).

Nothing special about those versions: they just happen to be the two WebKit-based browsers I have installed. But perhaps if you can spot the difference between those, it'll give a clue to the Firefox behaviour too.

Reply?

(a limited set of Markdown is supported)

Re #19: Text on the same line as the reference.

A second paragraph, following the reference.

The first paragraph above is “Re #19: Text on the same line as the reference.” I'm testing a hypothesis that if the comment starts with a reference, any following text in that para gets dropped.

Reply?

(a limited set of Markdown is supported)

Ha, interesting. If that's happening, it's a bug. The source of your comment is still around, though. Let me poke at it.

Reply?

(a limited set of Markdown is supported)

All right, all fixed.

I'd previously thought that reply lines should be a new block type in my comment-markdown. I miswrote the regex to recognize them, though, which ended up swallowing any text following (I'd intended lines with more text to just not be replies at all).

I've now patched it in a different way - reply lines start a new paragraph with a reply-to. Your comments are now revealed!

Reply?

(a limited set of Markdown is supported)

Re #18: I suspect it's a problem in parsing the background-size part of the shorthand. I'll verify that the current Chrome behavior is correct (I think it is). If so, I'll leave it as it is, because that's what standards are for. If not, I'll fix it. ^_^

Reply?

(a limited set of Markdown is supported)

Re #23: Did you figure out whether this is the correct behaviour or not? I created a minimum test-case at http://codepen.io/karaken12/pen/GveEh -- it works fine on Chrome 21, but looks terrible on Firefox 15.0.1.

Reply?

(a limited set of Markdown is supported)

Re #26: Yes, I verified that what I'm doing is the standards-compatible thing. Firefox just hasn't yet updated (nor have the mobile browsers).

Reply?

(a limited set of Markdown is supported)

I'd suggest changing the "Reply?" to a link which shows a form and hiding the reply form below each comment because those forms now take most of the space and distract from the actual comments themselves.

Reply?

(a limited set of Markdown is supported)

Re #28: In decent browsers, that's exactly what happens already - I'm using a <details> element to hide the comment form until you wish to see it.

I'm fine with legacy browsers not rendering my page as expected, since I'm following mature specs. ^_^

Reply?

(a limited set of Markdown is supported)