servo / servo/rust-url

Can data-url interoperate better with the mime crate?

Open
#567 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.6k
Forks
406
PR merge metrics
No merged PRs in 30d

Description

data-url has a Mime class distinct from the one in https://crates.io/crates/mime and it's looking like using data-url in servo as a replacement for https://crates.io/crates/base64 might mean redundantly parsing the mime type into both classes.

Could data-url:

  1. migrate to that mime class, or
  2. offer a codepath that just skips the mime-type parsing entirely, for use by client code that is already parsing its own mime type?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing data-url's Mime handling and how Servo uses it alongside the mime and base64 crates. Determine whether migration to the mime type or an API that skips duplicate parsing is appropriate; done means data-url provides one working interoperability path without redundant mime parsing.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.