mdn / mdn/browser-compat-data

css.properties.line-clamp.none - should be supported via `-webkit-line-clamp` property

Open
#25,231 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

alternative name browser:chrome data:css
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

the none value should be supported in chromium (via -webkit-line-clamp property)

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

add data

Did you test this? If so, how?

test in chrome M130

image

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

https://drafts.csswg.org/css-overflow-4/#propdef--webkit-line-clamp

https://drafts.csswg.org/css-overflow-4/#propdef-line-clamp

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-line-clamp

MDN metadata
MDN page report details
  • Query: css.properties.line-clamp
  • Report started: 2024-11-26T15:15:29.612Z

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 with the MDN page and CSSWG links in the issue, then inspect the browser compatibility data for css.properties.line-clamp. Confirm how Chromium support for the none value via -webkit-line-clamp is represented; done means the compatibility data includes the reported support for Chromium, Chrome, Edge 79+, Opera, and Samsung Internet.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend, web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.