Skip to content

Form: require user opt-in, and present the user with a summary of, browser/device info collection#24

Merged
jayaddison merged 9 commits intomainfrom
issue-22/browser-data-require-opt-in
Apr 6, 2026
Merged

Form: require user opt-in, and present the user with a summary of, browser/device info collection#24
jayaddison merged 9 commits intomainfrom
issue-22/browser-data-require-opt-in

Conversation

@jayaddison
Copy link
Copy Markdown
Member

Describe the reason for these changes and the problem that they solve

As described in #22, it is preferable to inform users about collection of information from their web browser environment before including it with their form submission, and the default should be that that information is not collected unless they consent/agree to doing that.

Briefly summarize the changes

  1. Add a consent checkbox that appears during the Form page in the feedback collection workflow.
  2. Add a translatable resource string (:warning: - currently English-language only) that provides a prompt about whether the user would like to include browser environment info.

How have the changes been tested?

  1. Local development testing.

Screenshots

image

List any issues that this change relates to
Resolves #22.
Builds-upon pull request #23.

This is required because the HTML DOM of the `Form` page contents
is cleared before the `data()` function is called.

If we do not store the element in a long-lived variable, then
when we run a query to find the `#browser-info-consent` HTML
element before the form is submitted, then we will not find it.
…2/browser-data-require-opt-in

Conflicts:
	dist/feedback.js
	dist/feedback.min.js
	src/pages/Form.js
… from non-EN locales

The fallback logic in the `i18n` module should handle selection
of the default (EN) version when a string is not present in
other locales.
…2/browser-data-require-opt-in

Conflicts:
	dist/feedback.js
	dist/feedback.min.js
	src/pages/Form.js
@jayaddison
Copy link
Copy Markdown
Member Author

jayaddison commented Apr 3, 2026

  • TODO: it would be nice to display to the user the list of browser details that were collected during the Review page phase. This could perhaps be placed within an HTML <details> element, because it may be verbose.

@jayaddison
Copy link
Copy Markdown
Member Author

  • TODO: it would be nice to display to the user the list of browser details that were collected during the Review page phase. This could perhaps be placed within an HTML <details> element, because it may be verbose.

This functionality is now included; at the review stage, the user is presented with the message text that they provided (if any), the browser-info collected (hidden by default, but expandable inside a <summary> HTML element), and the screenshot they included.

See below for an example of this review stage where browser information is included:

image

Base automatically changed from issue-21/configurable-browser-info-fields to main April 6, 2026 15:36
@jayaddison jayaddison changed the title Form: add checkbox, make browser-info inclusion non-default Form: require user opt-in, and present the user with a summary of, browser/device info collection Apr 6, 2026
@jayaddison jayaddison merged commit 0a8d8ee into main Apr 6, 2026
@jayaddison jayaddison deleted the issue-22/browser-data-require-opt-in branch April 6, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Feature: make browser env data require opt-in, and inform users about it

1 participant