Website and marketing terms beginning with F

Faceted navigation

Faceted navigation lets people filter a collection using attributes such as category, size or price. Its implementation can create many URL combinations. Agree which views have a useful public purpose and review crawling and indexing controls without breaking the filters customers need.

Also called: faceted search

Failover

Failover switches relevant work or traffic to an alternative component when the primary arrangement is considered unavailable. Its detection, routing and data readiness determine the result. Review the actual recovery process and verify the business task; an alternative server existing does not by itself prove that a transition preserves every operation.

Falsy

A falsy JavaScript value is treated as false in a Boolean context. Different representations can share that conditional behaviour without having the same business meaning. Ask which values the feature receives and how the actual condition interprets them, particularly where missing information and an explicitly false state require different useful customer feedback.

Favicon

A favicon is the small site icon a browser may show beside a page title, bookmark or tab. A simple recognisable version of your logo helps people spot your site among open tabs. It should remain readable at tiny sizes rather than reproduce every detail of the full logo.

Also called: site icon

Feature detection

Feature detection checks whether the current browser supports a capability before using it. It helps an application choose an appropriate supported path or fallback. Review the fallback task too; detecting an API’s presence alone does not establish that permission is granted or the intended action will succeed.

Feature flag

A feature flag controls whether particular functionality is enabled without necessarily changing all deployed code. It can support staged releases or quick disabling of a feature. Keep ownership, default behaviour and removal plans clear so old flags do not become confusing hidden configuration.

Also called: feature toggle

Featured snippet

A featured snippet is a search result presentation that highlights an answer extracted from a page. The search engine chooses whether to show one. A clear explanation can be useful to readers, but neither a particular word count nor a special tag guarantees this placement.

Fetch API

The Fetch API lets web code make requests and work with responses through a Promise-based interface. Receiving a response still requires checking its status and interpreting the relevant content. For a Jersey business, review the intended destination, unsuccessful results and customer feedback; fulfillment of fetch does not by itself establish that an enquiry, booking or other business action succeeded.

Also called: fetch()

Fetch Headers object

The Fetch API Headers interface provides methods for working with request and response header lists, subject to the relevant restrictions. It helps represent technical request information rather than establish permission or business success. Review the actual supported headers and receiving contract with the maintainer instead of assume an assigned value can always be sent or read.

Also called: Headers interface

Fetch Request object

The Fetch API Request object represents a resource request. Creating the object is separate from making that request and interpreting the eventual response. Record the intended destination, task and information with the maintainer, then review the receiving outcome rather than use an object’s existence as evidence that work reached the service.

Also called: Request interface

Fetch response clone

The Response clone method creates another Response for use before the original body has already been consumed; cloning after consumption throws an error. It supports relevant multiple-use cases in code. Ask why the feature needs a clone and review the actual reading paths rather than assume the method verifies or refreshes the information.

Also called: Response.clone()

Fetch response JSON

The Response json method reads the response body and returns a Promise for the result of parsing its text as JSON. The result can be any supported JSON value, not only a record-shaped object. Parsing is separate from confirming the data has the fields and meanings the business feature expects.

Also called: Response.json()

Fetch response OK

The Response ok property is true for a response status from 200 to 299. It is a technical status indication rather than proof that a particular booking, enquiry or other business outcome exists. Interpret the service’s returned information and result contract before displaying a stronger customer confirmation.

Also called: Response.ok

Fetch response status

The Response status property provides the response’s HTTP status code; some response types expose zero. Its meaning needs interpretation in the actual request workflow. Have the maintainer explain relevant successful and unsuccessful cases, and keep status handling separate from verifying the business information or action represented by the response.

Also called: Response.status

Fetch response text

The Response text method reads the response body and returns a Promise for its UTF-8-decoded string. Receiving that string is separate from interpreting its content or presenting it appropriately in a website feature. Review the expected information and actual customer outcome rather than treat body reading as complete business verification.

Also called: Response.text()

Fetch response type

The Response type property identifies the response category and affects whether scripts can access its headers and body. It is separate from the content’s format or business meaning. Review the actual access arrangement with the maintainer rather than assume receiving a response always makes its information available to the feature.

Also called: Response.type

Fieldset

A fieldset groups related form controls, usually with a legend naming the group. It can help people understand a set of options, such as delivery choices. Review both the visible grouping and its underlying structure so that the relationship remains understandable when a customer uses assistive technology.

Also called: form group

File API

The File API lets a web application work with files made available by the user, such as through a file input or drag and drop. It provides file information and reading capabilities. Review the implemented task and any later transfer separately; making a file available to a browser feature does not establish that the business received it.

File archive

A file archive packages files and associated structure into an archive format, sometimes with compression. It can support distribution or storage, but creating one does not prove that every required item was included or can be restored. A Jersey business should review the contents, destination and recovered result using the actual tools chosen for the handover.

Also called: Archive file

File checksum

A file checksum is a computed value used to compare file content through a specified algorithm. Hash-based checks operate on the content rather than simply its name. Record the algorithm and trusted reference alongside the comparison; a matching value is separate from checking whether the package is complete, current and appropriate for the intended task.

Also called: File hash

File directory

A file directory organises files and other directories in a filesystem hierarchy. It is a stored-location concept, separate from a website’s business-listing directory. Document which project material belongs in the location and review its actual contents; a familiar folder name does not prove that it contains the current approved sources.

Also called: Filesystem directory, File folder

File download

A file download obtains a file from a service or browser-generated resource for use on a device. A link click starts an action; it does not establish that the person received and opened the intended file. For a Jersey business, check the document version, browser outcome and usable contents before accepting a download feature or interpreting its reporting.

Also called: downloading a file

File extension

A file extension is the filename suffix commonly used to indicate a file type or associated application. Renaming the extension does not convert the underlying file into that format. Review the actual content and required application when receiving website assets rather than accept a familiar-looking suffix as proof of compatibility or a correct export.

Also called: Filename extension

File input accept

The accept setting supplies file-type hints to a browser’s file-selection control. It helps guide the customer towards expected formats, with appropriate instructions beside the input. The receiving application still needs its own validation; a picker hint does not establish that every selected or submitted file meets the business’s supported rules.

Also called: file accept attribute

File input multiple

The multiple setting allows a file-selection input to accept more than one chosen file. Review the customer instructions and the feature’s handling of the collection. The receiving workflow should have a clear meaning for each attachment, including the supported number and limits, rather than assume that selecting several files guarantees their acceptance.

Also called: multiple file input

File last modified

File.lastModified reports a file’s modification date as milliseconds since the Unix epoch; an unknown date can be represented by the current date. Keep this metadata’s meaning clear in the feature. A displayed timestamp is insufficient evidence that a document is the approved version or that its business information is current.

Also called: File.lastModified

File object

A browser File object provides file information and access to its contents, building on the Blob interface. It commonly comes from a user’s selection or drag and drop. Ask which file the feature is processing and verify the preview or receiving result, rather than treat the object’s presence as evidence of an accepted attachment.

Also called: File interface

File path

A file path identifies a location within a filesystem using the naming and path rules of that environment. Absolute and relative paths have different interpretation requirements. A Jersey business should record the machine or environment, intended location and relevant starting directory; a plausible-looking path does not establish that a file exists or that an operation will affect the right material.

Also called: Filesystem path

File permissions

File permissions govern supported access operations on filesystem material within the actual operating-system arrangement. For example, OpenBSD file modes include permission information managed through tools such as chmod. Have the maintainer document the authorised account and required access for the task rather than assume that successful login grants permission to change every file.

Also called: Filesystem permissions

File size

File size describes the amount of data in a file, commonly measured in bytes and larger units. Browser File objects expose their byte size through the inherited Blob interface. Record the actual value, unit and file version when comparing exports; a smaller file is separate from evidence that its important contents remain suitable.

Also called: File byte size

File system

A file system provides an arrangement for storing and retrieving files on storage devices, including rules for names and locations. Directories organise files within that arrangement. A Jersey business should understand where its website material is kept and how the maintained tools use it; storage organisation alone does not establish a complete backup, access policy or verified recovery process.

Also called: Filesystem

File upload

A file upload transfers a file from a device to a receiving service, such as a website handling an enquiry attachment. Choosing a file is only the selection stage. For a Jersey business, explain accepted formats and limits, review the server’s checks and access rules, then verify the received document and the customer’s confirmation through the actual workflow.

Also called: uploading a file

FileList

FileList represents the files provided through a supported browser file selection or drop operation. Its length indicates the number of files, and individual items are File objects. Review how the feature handles the selected collection and displays its next step; a list of chosen files is separate from successful transmission and receiving checks.

FileReader

FileReader reads File or Blob data asynchronously for a browser feature. It cannot simply read a user’s arbitrary file by its pathname. Keep the selected input and intended output clear, and review the actual preview or processing task before assuming that reading data establishes a later upload, save or staff-visible record.

FileReader data URL

FileReader.readAsDataURL() reads a File or Blob and exposes a data URL containing a base64 representation when the operation completes. The result includes the data URL declaration as well as the encoded content. Review the consuming feature and actual output; this reading operation does not establish that a receiving server stored the file.

Also called: FileReader.readAsDataURL()

Firewall

A firewall applies rules to network traffic, allowing or restricting communication. Different products operate in different places and have different capabilities. It forms one part of security; it does not replace updated software, appropriate account permissions or a recovery plan for the business.

First user source

First user source is a Google Analytics user-scoped dimension associated with the source of the user’s first measured acquisition. It differs from a later session’s source. Interpretation depends on the measurement identity and coverage, so it should not be treated as a complete historical account of how a person first discovered the business.

FLAC

FLAC stands for Free Lossless Audio Codec. It compresses audio without losing information from the signal supplied to that encoding process. It does not prove that the original recording was clear or repair information lost earlier. Keep the source identifiable and check the delivery arrangement when publishing audio on a website.

Also called: Free Lossless Audio Codec

Flex basis

The CSS flex-basis property sets a flex item’s initial main size within the supported layout calculation. It is separate from a promise about the final visible size. Review it alongside growth, shrinking, content and available space, then inspect the actual item rather than approve a basis value without checking the result.

Also called: flex-basis

Flex direction

The CSS flex-direction property defines the flex layout’s main axis and its normal or reversed direction. Its visible consequence needs review with the actual content and writing arrangement. Ask the maintainer to explain the chosen direction, then check meaningful order and supported keyboard use rather than assume a reversed appearance changes every navigation sequence.

Also called: flex-direction

Flex grow

The CSS flex-grow property sets an item’s factor for receiving positive free space along the flex container’s main axis. It concerns allocation of extra space rather than directly guarantee equal final widths. Review actual starting sizes, content and related settings before interpreting how the completed arrangement should look.

Also called: flex-grow

Flex shrink

The CSS flex-shrink property sets an item’s shrink factor when a flex line needs to distribute negative free space. It participates in the sizing calculation rather than guarantee all content becomes readable in any width. Review the actual labels and constraints with the maintainer, including the intended response when space is insufficient.

Also called: flex-shrink

Flex wrap

The CSS flex-wrap property controls whether flex items remain on one line or can wrap onto multiple lines, with relevant line-stacking behaviour. Review real labels and available space when deciding the arrangement. Wrapping is a layout capability rather than a guarantee that every resulting line forms an understandable content group.

Also called: flex-wrap

Flexbox

Flexbox is a CSS layout system that distributes and aligns items along one main axis at a time, as a row or column. Items can also wrap onto multiple lines. For a Jersey business, review the actual content, wrapping and order in the available space; choosing Flexbox does not by itself make a website feature readable, accessible or complete.

Also called: CSS Flexible Box Layout

Floating-point number

A floating-point number is a numeric representation with finite precision and range. JavaScript Number uses a binary floating-point format, so some decimal values cannot be stored exactly. For a Jersey website, agree the accepted precision, calculation and display rules with the maintainer, then review representative results; rounded presentation does not by itself establish exact stored values or suitable receiving information.

Also called: floating point

Flow control

Network flow control manages transmission with regard to what the receiving side can accept. It differs from congestion control addressing conditions along the network path. In TCP, the advertised receiver window participates in this arrangement. Ask the network maintainer to interpret an actual diagnostic result before changing generic settings.

Focus indicator

A focus indicator shows which link or control is currently selected for keyboard interaction. It helps a visitor understand where the next action will occur. Keep it visible against the surrounding design and avoid hiding it simply because the default outline feels unfamiliar.

Also called: focus ring, visible focus

Focus order

Focus order is the sequence in which interactive elements receive focus during sequential navigation. It should preserve meaning and usable operation. Review the actual page and changing components with a keyboard, checking that movement remains understandable when layouts, dialogs or form messages appear.

Also called: tab order

Foreign key

A foreign key links a database row to referenced values under a defined relationship constraint. It helps keep related records consistent, such as a booking referring to an existing customer. A Jersey business should review the actual enforcement and deletion rules; a relationship between records does not itself prove correct permissions, ownership or customer-facing information.

Form label

A form label identifies what an input control asks for and should be properly associated with that control. It helps people understand and operate fields, including with assistive technology. A Jersey business should use clear, lasting labels alongside suitable instructions and errors, then check the completed form rather than rely on placeholders.

Also called: field label

Form no validate

The HTML form novalidate attribute disables interactive browser constraint validation during submission. It does not remove the receiving system’s validation responsibility. Ask which feedback mechanism the chosen implementation uses and review the complete correction route, so disabling native checks is accompanied by appropriate field rules, useful messages and receiving assessment.

Also called: novalidate

FormData

FormData is a web interface for assembling named values, including files, in a form-style entry list that can be sent in a request. It helps a developer prepare information for transmission. For a Jersey business, check the actual fields, receiving system and customer feedback separately; creating the object does not establish that an enquiry arrived or was processed.

Also called: FormData interface

FormData append

The FormData append method adds a value for a name, retaining existing values with that name. This supports repeated entries when the feature needs them. Agree whether the receiving workflow expects one or several values, then review a representative repeated-entry case; adding an entry does not itself transmit the information.

Also called: FormData.append()

FormData delete

FormData.delete() removes a named entry and its values from the prepared object. Review why the feature removes that information and whether the receiver still receives the fields it needs. Changing the local entry list is separate from deleting a previously submitted enquiry or changing a record stored by another service.

Also called: FormData.delete()

FormData entries

FormData.entries() provides an iterator over the prepared object’s name-and-value pairs. A name can occur more than once, so review the expected repeated entries with the receiving workflow. Inspecting this list helps check preparation; it does not establish that the information was sent, accepted or processed by the business.

Also called: FormData.entries()

FormData get all

The FormData getAll method retrieves an array of values associated with a name, returning an empty list when none are present. It helps inspect repeated entries in the prepared object. Review the actual receiving interpretation separately, since seeing collected values in the browser does not establish that they were delivered or processed.

Also called: FormData.getAll()

FormData keys

FormData.keys() provides an iterator over the names in the prepared object, including repeated names where present. It helps inspect the field structure. Agree which fields the receiver expects and check the associated values separately, since a list of names alone does not establish complete information or a delivered enquiry.

Also called: FormData.keys()

FormData set

The FormData set method assigns a value for a name, replacing existing values with that name or creating the entry when absent. It differs from append, which retains earlier values. Review the intended single or repeated field meaning with the receiver, so a replacement does not silently remove information the business expects.

Also called: FormData.set()

FormData values

FormData.values() provides an iterator over values in the prepared form-data object, which may include strings and Blob objects. Keep their field meanings clear when reviewing the feature. Seeing values in the browser is useful preparation evidence, while the receiving interpretation and customer outcome need verification through the actual enquiry workflow.

Also called: FormData.values()

Frame ancestors

Frame ancestors is a Content Security Policy directive governing which parent documents may embed the protected document. It can support clickjacking protection. It differs from controlling which frames your page loads, so review the direction of the embedding relationship and the site’s legitimate integration requirements before changing the policy.

Also called: frame-ancestors directive

Frontend

Frontend development builds the website presentation and interaction people use in their browser, including content structure, styling and controls.

Also called: front end, front-end

FTP

FTP stands for File Transfer Protocol, a protocol for exchanging files between systems. Protection arrangements must be identified separately rather than inferred from the name. When a supplier discusses website transfers, ask which actual protocol, service and supported security configuration are used, then verify the intended destination and received files.

Also called: File Transfer Protocol

FTPS

FTPS refers to FTP protected with TLS in a supported arrangement. RFC 4217 describes a mechanism for FTP clients and servers to use TLS security and authentication. It differs from SFTP over SSH. Have the maintainer document the actual service and client requirements rather than interchange the two names in a hosting handover.

Also called: FTP with TLS

Fulfilment location

A fulfilment location identifies where or through which configured service an order is supplied. In a shop platform it can represent a store, warehouse or connected fulfilment arrangement. Keep inventory and shipping configuration aligned with the actual location; adding a location record does not automatically establish usable stock or delivery options.

Also called: Fulfillment location

Full stack

Full stack describes work across both frontend and backend parts of an application. Its exact scope varies by project and team. Ask which interface, service, data and release responsibilities are included instead of assuming the phrase covers every supplier, security review or maintenance task.

Also called: full-stack development

Function

A programming function groups instructions for a particular operation and can accept inputs or return a result. The actual language defines its behaviour. Ask how an important operation is tested and how its result connects to the wider customer workflow rather than judging it from its name alone.

Also called: programming function

Funnel exploration

A funnel exploration reports measured progress through a defined sequence of website or app steps. It can help identify where a customer task appears to stop. The event definitions, sequence settings, filters and coverage determine the result. A Jersey business should check the measurement and working journey before treating a reported drop-off as a proven cause.