You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.bs
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -316,12 +316,15 @@ Using `full-address` to enable comprehensive address autofill:
316
316
317
317
# Security and Privacy Considerations # {#security-privacy}
318
318
319
-
## Timing Attacks ## {#timing-attacks}
320
-
321
319
The {{AutofillEvent}} exposes autofill values to JavaScript before they are committed to form
322
320
fields. User agents SHOULD ensure that the event is only fired after explicit user consent to
323
321
autofill has been given (e.g., by selecting an autofill suggestion from a dropdown).
324
322
323
+
The data passed to the event is limited to data that the user agent intends to fill into forms on the page, given that the API shape requires an element as the key to the autofill values.
324
+
325
+
Note that when the event fires after a `refill()` call, the form is likely to include new fields that weren't present the first time the user agent filled the form. The user agent should
326
+
still consider user consent before filling in the new form fields, as is already the case for automatic refills in user agents that support them.
0 commit comments