Automattic / Automattic/jetpack

Forms: the submitted content doesn't blend in theme

Open
#29,528 3 comments 0 reactions 0 assignees View on GitHub
[Block] Form [Feature] Forms [Package] Forms [Plugin] Jetpack [Pri] Normal Bug Customer Report [LEGACY] Enhancement
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

### Impacted plugin

Jetpack

### Quick summary

The submitted content that you'll see after submitting the form styled by the block, therefore it doesn't fit in themes. We should remove the style as much as possible so that it blends in the theme.

This is an example with TT3:
![Screenshot 2023-03-17 at 10 47 13](https://user-images.githubusercontent.com/908665/225886194-d585046b-5eff-4b0e-9649-b5395198b6b9.jpg)

Things to remove:
* Remove the color and font weight from the "go back" link
* Remove the font weight and the margins from he `h4` "Your message has been sent" (why `h4`?)
* Remove the font weight from the field name
* Remove the font weight from the field value
* Remove the width and the paddings from the `.contact-form-submission`

cc: @jeffikus

### Steps to reproduce

1. Add a form
2. Submit the form
3. See the submitted content on the page

### A clear and concise description of what you expected to happen.

_No response_

### What actually happened

_No response_

### Impact

All

### Available workarounds?

No but the platform is still usable

### Platform (Simple and/or Atomic)

_No response_

### Logs or notes

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the Jetpack form submission with the TT3 theme and inspect the submitted-content styles, especially the go-back link, h4 message, field names and values, and .contact-form-submission. The issue names no files or tests; done means those elements inherit the theme without the listed font, margin, width, color, or padding overrides.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, php, wordpress
Domain
design, frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.