fix: add font weight to helptext css so that it inherits the right weight to all HTML and markdown elements

[walldenfilippa]

Description

Moved font-weight from .helpTextContent span to .helpTextContent, since we want more than just the span element to avoid inherited bold styling from .ds-label (font-weight: 500).

Related Issue(s)

• closes #4130

Verification/QA

• Manual functionality testing
  • I have tested these changes manually
  • Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
  • No testing done/necessary
• Automated tests
  • Unit test(s) have been added/updated
  • Cypress E2E test(s) have been added/updated
  • No automatic tests are needed here (no functional changes/additions)
  • I want someone to help me make some tests
• UU/WCAG (follow these guidelines until we have our own)
  • I have tested with a screen reader/keyboard navigation/automated wcag validator
  • No testing done/necessary (no DOM/visual changes)
  • I want someone to help me perform accessibility testing
• User documentation @ altinn-studio-docs
  • Has been added/updated
  • No functionality has been changed/added, so no documentation is needed
  • I will do that later/have created an issue
• Support in Altinn Studio
  • Issue(s) created for support in Studio
  • This change/feature does not require any changes to Altinn Studio
• Sprint board
  • The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
  • I don't have permissions to do that, please help me out
• Labels
  • I have added a kind/* and backport* label to this PR for proper release notes grouping
  • I don't have permissions to add labels, please help me out

[coderabbitai]

📝 Walkthrough

Walkthrough

The Helptext.module.css stylesheet is updated to normalize font-weight styling. The font-weight: 400 declaration is moved from a nested span rule to the .helpTextContent container level, consolidating typography control and preventing unintended bold rendering in help text fields.

Changes

Help text font-weight normalization

Layer / File(s)	Summary
Help text container font-weight styling src/app-components/HelpText/Helptext.module.css	The .helpTextContent CSS rule now explicitly sets font-weight: 400 at the container level, replacing the prior nested span rule that targeted the same weight. This ensures consistent, non-bold text rendering across help text content.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding font weight to helptext CSS to ensure proper inheritance of font weight to all HTML and markdown elements.
Linked Issues check	✅ Passed	The code changes directly address the objective in issue #4130 by moving font-weight from span-specific styling to the container level, ensuring consistent font weight inheritance across all HTML and Markdown children elements.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to fixing the font-weight inheritance issue in the helptext component CSS file, with no extraneous modifications present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The PR description is comprehensive and addresses all major sections of the template with appropriate detail.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/4130-fontweight-help-text

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[lassopicasso]

Nice 👍

[github-actions]

✅ Automatic backport successful!

A backport PR has been automatically created for the release/v4.30 release branch.

The release branch release/v4.30 already existed and was updated.

The cherry-pick was clean with no conflicts. Please review the backport PR when it appears.