GateTrue

What each generator documents about marking its output

Request parameter: control written as a field

A request parameter is a field in a call whose value decides what the output carries. One entry here publishes a boolean watermark field, its default, and the stamp it produces when set. As of 2026-09-22.

What a field, a type and a default together establishA named field with a documented type says control exists and where it lives. A published default says what happens when nobody sets it, which is the ordinary case. A description of the resulting stamp says what setting it does to the frame.Published about one parameterThe fieldA name and a type, so a caller knows control exists and where toput it.The defaultFalse, so the ordinary outcome without a decision is unmarkedoutput.The effectThe text of the stamp and the corner it occupies, when the fieldis set.Still unstatedSize and opacity, other surfaces, and anything at all about thefile.The most precise control value in the register
Fig. 1 A plan benefit says removal is permitted. A default says what actually happens in the absence of instruction.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termRequest parameter
What it namesA field in a call whose value decides what output carries
What it is notA plan benefit, or a setting inside a product
Where the register uses itOne entry's control value

Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.

1Why it is the most precise value in its column

Every other control value here is a mechanism named in a few words: a plan benefit, a setting, nothing published. This one has a field name, a type, a documented default, and a description of what setting it does to the frame. A reference exists to be exact about inputs, and the marking answer inherits that.

It also inverts the usual question. Elsewhere the column asks what it takes to remove a mark that is applied by default. Here nothing is applied unless a caller asks, so the interesting question is who would ask and why.

2What a documented default is worth

Defaults decide what happens when nobody thinks about a question, which is most of the time. A published default of false means the ordinary outcome for an integrated product is unmarked output, without anybody having made a decision.

That is a stronger statement than a plan benefit, because it describes behaviour rather than entitlement. A plan benefit says removal is permitted; a default says what actually happens in the absence of instruction.

3What it still does not settle

Whether the parameter is honoured in every configuration, what the mark looks like beyond the words and the corner, and what happens on other surfaces. One entry answers the last of those, by documenting a console that stamps regardless.

And nothing about the file. The same reference that specifies a stamp down to its corner lists no metadata field among the parameters or the response, so a caller can control the frame precisely and can promise nothing about what the file says.

Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: documented default, limitations section, verification platform.