File: heuristics.rst

package info (click to toggle)
firefox 134.0.2-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,345,684 kB
  • sloc: cpp: 7,244,582; javascript: 6,236,669; ansic: 3,654,775; python: 1,359,774; xml: 618,542; asm: 426,944; java: 183,315; sh: 66,206; makefile: 19,398; perl: 13,009; objc: 12,453; yacc: 4,583; cs: 3,846; pascal: 2,989; lex: 1,720; ruby: 1,194; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
file content (48 lines) | stat: -rw-r--r-- 1,985 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
Form Autofill Heuristics
========================

Form Autofill Heuristics module is for detecting the field type based on `autocomplete attribute <https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill>`_, `the regular expressions <https://searchfox.org/mozilla-central/source/toolkit/components/formautofill/shared/HeuristicsRegExp.sys.mjs>`_ and the customized logic in each parser.

Debugging
---------

The pref ``extensions.formautofill.heuristics.enabled`` is "true" in default. Set it to "false" could be useful to verify the result of autocomplete attribute.

Dependent APIs
--------------

``element.getAutocompleteInfo()`` provides the parsed result of ``autocomplete`` attribute which includes the field name and section information defined in `autofill spec <https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill>`_

Regular Expressions
-------------------

This section is about how the regular expression is applied during parsing fields. All regular expressions are in `HeuristicsRegexp.sys.mjs <https://searchfox.org/mozilla-central/source/toolkit/components/formautofill/shared/HeuristicsRegExp.sys.mjs>`_.

Parser Implementations
----------------------

The parsers are for detecting the field type more accurately based on the near context of a field. Each parser uses ``FieldScanner`` to traverse the interested fields with the result from the regular expressions and adjust each field type when it matches to a grammar.

* _parsePhoneFields

  * related type: ``tel``, ``tel-*``

* _parseStreetAddressFields

  * related type: ``street-address`, `address-line[1-3]``

* _parseAddressFields

  * related type: ``address-level[1-2]``

* _parseCreditCardExpiryFields

  * related type: ``cc-exp``, ``cc-exp-month``, ``cc-exp-year``

* _parseCreditCardNameFields

  * related type: ``cc-name``, ``given-name``, ``additional-name``, ``family-name``

* _parseCreditCardNumberFields

  * related type: ``cc-number``