Filliny buying guide: Two fields say “Quantity.” Do you know what belongs in each?

Assess only the preflight value of test mode and highlighting. Finding two inputs doesn't show that their identical labels have been interpreted correctly.

Source: chromewebstore.google.com
October 30, 2026
2 min

The developer’s store listing for Filliny distinguishes two checks: one highlights detected fields, and the other checks a form with mock data. That matters when reviewing your own sample forms with no real data. Seeing two inputs establishes coverage of two positions; it doesn't establish that each example value suits its intended purpose. This guide doesn't evaluate automated filling or submission on real sites.

Both fields say “Quantity,” but mean different things

Draw two groups of paper input fields. Put “Quantity” under “Items per tray,” expecting 3 per tray. Put the same label under “Spare box,” expecting 8 spares. Give a reviewer a card showing only the two highlighted positions. Ask them to record “positions found” separately from “evidence that the values make sense in context.” They can count two for the first. For the second they need the group headings and mock values.

Now consider a mock result where both fields have numbers, but the values are reversed: 3 spares and 8 per tray. Detection still passes; the check of meaning fails. If the group headings are hidden, don't guess which value belongs where just to get a pass. Conversely, if the second group is never detected, record a gap in coverage first; don't roll it into the check of meaning. These are paper cards. No extension is loaded and nothing is entered on a webpage.

For a few fixed fields, checking by hand is simpler

If your team frequently maintains sample forms with different structures and needs to test coverage separately from mock input, this kind of preflight check is worth comparing. For one fixed page, label the roles of the fields and walk through them by hand. The developer's extension disclosure lists web content among the data it handles. Mock values in test mode say nothing about the extension's reach on its own. Evaluate it only with a self-made sample form with no real data. Keep the manual check for pages you can't expose to the extension.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:chromewebstore.google.com