minmax() Track Bounds Semantics Lookup
Resolve supported minmax maximum-bound semantics; caller independently establishes valid minimum (fr minimum unsupported). Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.
Description
Grid minmax separates a minimum track constraint from a maximum sizing function.
Grid minmax separates a minimum track constraint from a maximum sizing function.1
A short maximum-token note does not solve intrinsic track sizes. Use minmax() Track Bounds Semantics Lookup to look up a supported term.
When to use minmax() Track Bounds Semantics Lookup
Use minmax() Track Bounds Semantics Lookup to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.
How to use minmax() Track Bounds Semantics Lookup and understand its results
- Choose the exact supported token from the table; preserve its punctuation and capitalization.
- Enter Maximum token using the field table and validation rules below, then run the tool.
- Read Meaning and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| maximumToken | Maximum token | string | Required; constraints below |
Enter one of the exact supported maximumToken tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.
meaning = storedTable[exactSupportedToken] Field order, units and branch conditions follow the implementation explanation above.
| Exact supported token | Stored meaning |
|---|---|
| fixed | maximum cannot shrink below the minimum; used max is at least min |
| fr | flexible maximum shares remaining space after intrinsic minimum resolution |
| auto | automatic maximum participates in eligible alignment stretching |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"maximumToken": "fr"
},
"output": {
"meaning": "flexible maximum shares remaining space after intrinsic minimum resolution"
}
}Limitations and assumptions
A short maximum-token note does not solve intrinsic track sizes. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use shape-outside Float Text-Wrap Note for a related task: Shape-outside influences wrapping around an eligible float.
Use Grid fr Free-Space Share Calculator for a related task: Fractional grid tracks share independently resolved remaining space.
References
-
minmax() Track Bounds Semantics Lookup — tool.io
Similar or alternative tools
- shape-outside Float Text-Wrap Note
Shape-outside influences wrapping around an eligible float.
- Grid fr Free-Space Share Calculator
Fractional grid tracks share independently resolved remaining space.