Next.js website for Rocky Mountain Vending company featuring: - Product catalog with Stripe integration - Service areas and parts pages - Admin dashboard with Clerk authentication - SEO optimized pages with JSON-LD structured data Co-authored-by: Cursor <cursoragent@cursor.com>
36 lines
No EOL
1.3 KiB
Text
36 lines
No EOL
1.3 KiB
Text
export default AutocompleteAudit;
|
|
/**
|
|
* The autocomplete attribute can have multiple tokens in it. All tokens should be valid and in the correct order.
|
|
* For example, cc-namez is an invalid token. tel mobile shipping section-foo are valid tokens, but out of order. The spec defines correct ordering, but in short, correct order is:
|
|
*
|
|
* [section-*] [shipping|billing] [home|work|mobile|fax|pager] <autofill field name>
|
|
*
|
|
* If either of these invalid situations, the autocomplete property will be an empty string. */
|
|
declare class AutocompleteAudit extends Audit {
|
|
/**
|
|
* @param {LH.Artifacts.InputElement} input
|
|
* @return {{hasValidTokens: boolean, isValidOrder?: boolean}}
|
|
*/
|
|
static checkAttributeValidity(input: LH.Artifacts.InputElement): {
|
|
hasValidTokens: boolean;
|
|
isValidOrder?: boolean;
|
|
};
|
|
/**
|
|
* @param {LH.Artifacts} artifacts
|
|
* @return {LH.Audit.Product}
|
|
*/
|
|
static audit(artifacts: LH.Artifacts): LH.Audit.Product;
|
|
}
|
|
export namespace UIStrings {
|
|
let title: string;
|
|
let failureTitle: string;
|
|
let description: string;
|
|
let columnSuggestions: string;
|
|
let columnCurrent: string;
|
|
let warningInvalid: string;
|
|
let warningOrder: string;
|
|
let reviewOrder: string;
|
|
let manualReview: string;
|
|
}
|
|
import { Audit } from './audit.js';
|
|
//# sourceMappingURL=autocomplete.d.ts.map |