servo/servo

Provide actual messages in JS errors

Open

#40,756 opened on Nov 20, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Rust (3,630 forks)batch import
good first issue

Repository metrics

Stars
 (36,724 stars)
PR merge metrics
 (Avg merge 2d 14h) (556 merged PRs in 30d)

Description

Now that each error variant accepts Option<String> (#39053), we should start to write actually error messages instead of passing None.

OFF-TOPIC: Should we accept Cow rather than string? Or maybe even create JSString directly? (probably not).

Contributor guide

Research direction
Find error variants that currently pass 'None' and replace them with descriptive error messages. Consider whether to accept Cow<str> or JSString for better memory efficiency.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65