hidden=until-found Find-In-Page Lookup

Bounded HTML feature/convention note; no full document audit or live browser compatibility determination.

Description

hidden=until-found Find-In-Page Lookup: look up a supported built-in reference entry.

A hidden-until-found element can participate in browser-driven revelation under supported HTML behavior. That differs from ordinary always-hidden content.1

This tool returns a built-in reference entry for an exact supported selector. The supported entries and their scope are part of the tool; no website or current external table is queried.

When to use this tool

Use this tool when the supplied inputs match the specific operation described above and you need a repeatable result under its stated convention.

  • Check the supported input and output contract against an existing calculation or observation.
  • Use the complete example to confirm units, selector spelling and result interpretation.

How to use the tool and how it works

  1. Enter every field in the input table using the stated units and the exact supported selector spelling where applicable.
  2. Run the tool. Correct input errors before interpreting an output.
  3. Read the result fields below; use accompanying flags and the stated sign, boundary or model convention when interpreting a number.

Accept until-found and return the built-in find-in-page and beforematch note.2

Input fieldMeaning and unitsAccepted input
topicTopic.Exact value: "until-found"
topicBuilt-in entry
"until-found"hidden="until-found" can allow find-in-page/fragment reveal with beforematch in supporting browsers; rendering/style and support constraints remain.
Output fieldInterpretation
resultObject containing the following named result fields.
result.referenceThe stored entry for the exact selected key; its type may be text, a number or a list.
json
{
  "input": {
    "topic": "until-found"
  },
  "output": {
    "result": {
      "reference": "hidden=\"until-found\" can allow find-in-page/fragment reveal with beforematch in supporting browsers; rendering/style and support constraints remain."
    }
  }
}

Limitations and assumptions

  • The lookup does not test browser support, event handlers, CSS or whether a particular document will reveal the element.
  • Every declared field is required and unexpected fields are rejected. Numeric inputs must be finite; input errors are distinct from a valid false result or an explicitly qualified output.
  • Extremely large inputs and nonfinite or excessively large outputs are rejected. List positions reported by the tool use zero-based indices unless stated otherwise.

Alternative or Complementary methods

Check the underlying observations, units and conventions independently before using the result in a larger workflow. The tools listed below address nearby tasks; compare their inputs and scope before substituting one for this operation.

References

  1. HTML Standard: the hidden attribute — WHATWG

  2. Tool behavior and example: hidden=until-found Find-In-Page Lookup — tool.io

Similar or alternative tools

  • Single h1 Per Page Rule Check

    Explicit caller observed h1 count against a one-h1 style rule; not a HTML parsing, standard validity or accessibility certification.

  • abbr title A11y Note Lookup

    Bounded HTML feature/convention note; no full document audit or live browser compatibility determination.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies