Skip to content

fix(text/javascript): Clarify charset validity in HTTP vs HTML contex… #40100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Shrinivassab
Copy link
Contributor

@Shrinivassab Shrinivassab commented Jun 27, 2025

Description

Updated text/javascript MIME type docs to clarify that charset is valid in HTTP headers.

Motivation

Fixes incorrect documentation that claimed charset is always invalid.

Additional details

Related issues and pull requests

Fixes #39505

@Shrinivassab Shrinivassab requested a review from a team as a code owner June 27, 2025 02:32
@Shrinivassab Shrinivassab requested review from hamishwillee and removed request for a team June 27, 2025 02:32
@github-actions github-actions bot added Content:HTTP HTTP docs size/s [PR only] 6-50 LoC changed labels Jun 27, 2025
Copy link
Contributor

Preview URLs

Flaws (3)

URL: /en-US/docs/Web/HTTP/Guides/MIME_types
Title: Media types (MIME types)
Flaw count: 3

  • unknown:
    • No generic content config found
    • no blog root
    • no blog root
External URLs (4)

URL: /en-US/docs/Web/HTTP/Guides/MIME_types
Title: Media types (MIME types)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:HTTP HTTP docs size/s [PR only] 6-50 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

charset is not invalid in text/javascript MIME
1 participant