Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Merge style_traits::ToCss trait into cssparser::ToCss

Open
#438 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
web-dev

Research direction

Start by comparing cssparser/src/serializer.rs#L14 with stylo/style_traits/values.rs#L78 to identify the differences between the two ToCss traits. Then inspect the style_derive macro and cssparser-macros to determine the merge scope. Done means the duplicated trait and macro functionality are consolidated without losing the existing behavior.

Written by the indexing model from the issue text.

Description

cssparser and style_traits both have ToCss that are very similar, but have some slight differences. In order to simplify implementations, I'm happy to do the work to merge these (including the macro from style_derive into cssparser-macros), but I wanted to make sure there wasn't a reason for the split before I got started?

Dominant language
Rust
Stars
869
Forks
152
Avg merge
15h 8m
Merged PRs (30d)
12

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.

More from servo/rust-cssparser

All issues in servo/rust-cssparser

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.