---
title: I went back and fixed the commas
description: >-
  Four of my Stack Overflow answers got edited years after I wrote them. Every single edit was
  grammar. The advice I left exactly where it was.
url: https://expiredqueues.com/answers-i-went-back-to-fix/
markdown: https://expiredqueues.com/answers-i-went-back-to-fix/index.md
date: '2026-05-16T10:00:00.000Z'
image: https://expiredqueues.com/images/og/answers-i-went-back-to-fix-95314ff5.jpg
---

Retrospect posts stack-overflow

# I went back and fixed the commas

16 May 2026 By Adrian Noel 3 min read

On this page

1. [Who made the edits](#who-made-the-edits)
2. [Still fine](#still-fine)
3. [Dead](#dead)
4. [The one that bothers me](#the-one-that-bothers-me)
5. [Why the advice doesn't get fixed](#why-the-advice-doesn-t-get-fixed)

I have sixty-four answers on Stack Overflow. Ten were edited after posting. Six of those edits were same-day typo fixes.

The other four were edited years later:

Days before the last edit

1. **3,424**
2. **2,860**
3. **1,834**
4. **1,448**

1) **Viewport meta** Sep 2013\
   Feb 2023
2) **Empty class** Jun 2015\
   Apr 2023
3) **Two-column** Jun 2015\
   Jun 2020
4) **Image sizing** Oct 2013\
   Sep 2017

Gap between posting an answer and the last time anyone edited it.

The longest gap is nearly ten years. Somebody edited a 2013 answer in February 2023.

## Who made the edits

The data doesn't say. Stack Overflow lets anybody with enough reputation edit your posts. The timestamp records the last edit, not who made it.

Some of the edits were mine. My English in 2013 wasn't what it is now, and at some point I went back and cleaned up the grammar. Others may have been strangers tidying up after me. I can't tell the two apart.

Nobody changed the advice, me included. Whoever edited had the answer open and didn't check whether it was still true.

So I went back through my answers and checked.

## Still fine

**[Is an empty `class` attribute valid HTML?](https://stackoverflow.com/a/30749192)** Yes, and it still is. I ran it through the W3C validator before answering, which is more rigor than I usually applied back then. Nothing to change.

**[Odd margin between inline-block elements](https://stackoverflow.com/a/18927094)** The whitespace gap is real, and `font-size: 0` on the parent still removes it. You wouldn't hit this today. You'd use flexbox and never see the gap. The answer is correct and no longer needed.

**[Why is box-sizing acting different on table vs div?](https://stackoverflow.com/a/19069106)** The observation holds. The explanation was a guess, and I said so in the answer: "FYI, I didn't find it anywhere document." It got five upvotes.

## Dead

**[Bootstrap 3 navbar active class](https://stackoverflow.com/a/19095814)** The answer says "Add `.navbar-default`." That class doesn't exist past Bootstrap 3. The answer has seven points and 35,000 views. The advice had a [hard expiry date](https://expiredqueues.com/answers-need-expiry-dates/index.md).

**[Modal open on page load](https://stackoverflow.com/a/20878053)** I told people to fake it with `.modal.in` and place a backdrop div by hand. Bootstrap 4 renamed `in` to `show`, and the trick stopped working. It was a hack when I wrote it.

## The one that bothers me

**[Meta viewport tag being ignored](https://stackoverflow.com/a/19080745)** It has 88,000 views. The core advice is still right: set `width=device-width, initial-scale=1` and don't hard-code widths.

Then I added this:

> And if you wanted disable zoom feature, set `user-scalable=no`

In 2013 that was routine. It's also the most user-hostile line I've published. It takes pinch-to-zoom away from people who need it, on a phone, permanently. [iOS Safari has ignored it for years](https://expiredqueues.com/stop-zoom-in-on-input-focus-on-mobile-devices/index.md), because enough developers like me kept shipping it.

That answer was edited in February 2023. The edit tidied the prose around that line. The line stayed.

## Why the advice doesn't get fixed

Nobody edits an answer that still works. The Bootstrap 3 answer still worked for anyone on Bootstrap 3. The viewport answer still worked. Nothing prompts you to revise.

Grammar is different. You can spot a grammar mistake at a glance. You can fix it without knowing the subject.

**Expired Queues is on YouTube.** Short videos on the same topics as this blog.

[Watch on YouTube](https://www.youtube.com/@expiredqueues)

[Previously Six weeks in 2013](https://expiredqueues.com/six-weeks-in-2013/index.md) [Next Every answer needs an expiry date](https://expiredqueues.com/answers-need-expiry-dates/index.md)

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "I went back and fixed the commas",
  "description": "Four of my Stack Overflow answers got edited years after I wrote them. Every single edit was grammar. The advice I left exactly where it was.",
  "datePublished": "2026-05-16T10:00:00.000Z",
  "dateModified": "2026-05-16T10:00:00.000Z",
  "author": {
    "@type": "Person",
    "name": "Adrian Noel",
    "url": "https://expiredqueues.com/about/"
  },
  "publisher": {
    "@type": "Person",
    "name": "Adrian Noel"
  },
  "mainEntityOfPage": "https://expiredqueues.com/answers-i-went-back-to-fix/",
  "keywords": "posts, stack-overflow, css, tips-tricks",
  "articleSection": "Retrospect"
}
```
