Why a healthy-looking diagnostic page kept printing undefined

Some people using a small diagnostic page were handed the nine-letter word undefined where their visitor address should have been. The page came back normally, with no crash and no blank screen. The wrong answer sat there looking respectable while it cost us time to find.

The job: take the first real answer of three

During a change in how visitor addresses reached the site, the page needed to choose the first real answer from three possible places. If the first place had nothing, it should try the second. If that had nothing, it should use the last one.

That is like picking the first ripe apple from three bowls. An empty first bowl should send you to the next bowl.

The fix that came too late

We first put the three choices into one short line and turned the final result into text. We expected that one step to make the answer safe to display. It did not. The conversion happened too late, because the page had already picked the wrong thing before it was turned into words.

The page runs on JScript, an older kind of JavaScript. In that environment, asking for a missing value does not give you an empty answer. It gives you an empty container.

Picture an empty jar on a kitchen counter. The jar has nothing in it, but it is still a jar. If someone asks whether there is something on the counter, the answer is yes. The program made the same mistake. It saw the first container, treated it as something worth choosing, and never looked at the second or third place where a real answer might be waiting.

When the page finally turned that empty container into text, it did not print a blank. It printed the literal word undefined.

That is why the bug was so slippery. A basic check could see that the page loaded. The response was successful. There was ordinary-looking text in the body. Nothing announced itself as broken. But for the visitors who needed the fallback path, the page was confidently telling them something untrue.

The shared routine that worked

A good piece of shared code had misled us. Elsewhere, one small routine was built to solve this exact problem. Before it chose among the three possible values, it cleaned each one separately. An absent value became a blank answer. A blank answer does not get picked, so the routine moved on to the next possibility.

That shared routine had been working. The three pages that failed did not use it. Each had a copied version of the same idea, with one tiny difference: they chose first and cleaned later.

What it cost

This was not a dramatic outage. No alarm goes off for a page that technically keeps working. The cost was investigation time, because the screen looked healthy. It cost patience, because a normal response had to be treated as suspicious. And three separate pages, including administrative work, could show the wrong thing before the pattern was clear.

The repair, and asking the page itself

Hiding the word undefined would only have covered the problem. The repair was to make each possible answer empty or usable before the page chose among them. Then a controlled request through every affected path returned a real value instead of the wrong word.

That check mattered. Reading a changed line of code and nodding at it is not the same as asking the page the question it must answer in real life.

The larger job came after the visible fix. We searched for other copies of the same shortcut. A shared, safer recipe and several hand-copied recipes had drifted apart. The old shared routine was protecting itself. The copies were not.

This has nothing to do with visitor addresses. A spreadsheet, a form, a customer email template, or a website page can all have the same problem. When a trusted version works and look-alikes exist elsewhere, each look-alike has to be checked for the same protection, and tested the way a visitor would use it.

The empty container was doing exactly what an empty jar does. It existed, it took up a slot, and it answered “is something here” with yes. JScript never lied to us. The page asked whether something was there, when it needed to ask whether the answer was usable before a visitor’s address got printed to a screen.

dxdev LESSON · paste into your AI coding agent
LESSON: A copy of a trusted routine is not trusted, so compare every look-alike against the original protection before calling one page fixed
SOURCE: dxdev.com/everyday-ai/page-that-said-undefined
WHAT HAPPENED: A small diagnostic page had to pick the first real value from three possible places while the way visitor addresses reached the site was changing. In the older JScript environment it ran in, asking for a missing value returned an empty container rather than an empty answer, so the first place always looked filled and the second and third were never tried. When the result was finally turned into text it printed the literal word undefined. The page loaded normally with a successful response, so basic checks passed. A shared routine elsewhere cleaned each of the three values first, so an absent one became blank and was skipped, but three pages, including administrative ones, used hand copied versions that chose first and cleaned later. Wrapping the final result in a text conversion did not work because it came too late. The repair was to make each candidate empty or usable before choosing, verified with a controlled request through every affected path, followed by a search for other copies.
THE RULE: A working shared routine proves nothing about its hand copied look-alikes. Normalize each candidate value before choosing among them, and test through the real request path instead of reading the changed line.
CHECK MY CODE, then report PASS or FAIL with file:line for each:
  1. Any fallback chain (first non empty of A, B, C) written inline that selects a value before normalizing missing or null values.
  2. Any hand copied version of a shared helper that does not call the shared helper itself.
  3. Any page or health check that confirms only a successful response and never asserts that the displayed value is real rather than the literal word undefined or null.
THEN PRINT: a table (check, PASS/FAIL, evidence, fix) + a verdict (applies / partially / OUT_OF_SCOPE / no) + the single most important next action.