mdn / mdn/rari

QA Notes for mdn-data being removed from rari

Open
#435 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
57
Forks
47
Avg merge
1d 11h
Merged PRs (30d)
68

Description

Relates to https://github.com/mdn/rari/pull/390.

Formal definition:

  1. Animation type value is a redirect to color in prod
Image

2. Changes in content - are they intended?
Test environment is missing some context when compared to Prod.

Image Image

3. Localization:

  • incomplete in DE and Japanese (see JA> yes)
Image Image

Layout:
In laptop half screen/ tablet/ mobile type of layouts, it can be noticed that the first column is smaller.

Image
What did you expect to see?

Links:
https://test.developer.allizom.org/en-US/docs/Web/CSS/Reference/Properties/corner-top-right-shape#formal_definition

  • improvement on some compared to prod, but probably missing some links (see border-radius), fit-content()
Image Image Image

https://test.developer.allizom.org/en-US/docs/Web/CSS/Reference/Properties/background-color#formal_definition
https://test.developer.allizom.org/de/docs/Web/CSS/Reference/Properties/max-width#barrierefreiheit
https://test.developer.allizom.org/en-US/docs/Web/CSS/Reference/Properties/border-inline-start#formal_definition

This issue is meant to share QA observations - changes may be intended.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

Contributor guide

Open the contributing guide

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 PR 390 and compare the linked test-environment pages with their production counterparts, including the listed CSS property pages. Confirm which differences in formal definitions, content links, localization, and responsive layout are unintended; done means documenting or resolving the confirmed discrepancies.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.