Status of dropped-during-experimental-phase elements

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
css
Domain
web-dev

Research direction

Start with the block-overflow and overflow-block entries in css/properties.json, then compare them with the linked MDN specification and the related mdn/data#314 issue. Determine how dropped or replaced experimental properties should be represented; the work is done when these entries consistently reflect the project’s chosen status or removal policy.

Written by the indexing model from the issue text.

Description

accepting PR

It's quite often that CSS proposals changes, and experimental elements disappear or get replaced.

For example, motion was dropped in favor of offset: https://github.com/mdn/data/issues/314

I also noticed both block-overflow and overflow-block exists in https://github.com/mdn/data/blob/master/css/properties.json. The current spec is using overflow-block, so I guess block-overflow was dropped in favor of it.

Can these properties be removed from the data? If not, I think currently there is no good status for them. Both deprecated and obsolete indicate the property was once supported in the browser.

Dominant language
JavaScript
Stars
787
Forks
216
Avg merge
1d 5h
Merged PRs (30d)
6

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.

More from mdn/data

All issues in mdn/data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.