microsoft / microsoft/vscode-css-languageservice

Bring back browsers information in hover cards

Open
#435 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
384
Forks
217
Avg merge
3d 16h
Merged PRs (30d)
14

Description

See: https://github.com/microsoft/vscode-css-languageservice/issues/427#issuecomment-2826498778


Not every team uses Baseline as their target and the previous implementation was agnostic of the specific targets in use for a given project.

While some developers might not immediately know from browser versions if something is sufficiently adopted for their case, others do know and do use it like that.

By only showing the baseline status a lot of information is hidden at first and only those teams using Baseline actually benefit from the recent change.

Can we maybe keep the current list of browser versions while also adding some Baseline related information?


@aeschli said:

@romainmenke Thanks for the feedback. I'm ok in bringing the browser section back, maybe below the baseline information.
I think its interesting for newly added properties.

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 reading the linked vscode-css-languageservice issue comment and locating the hover-card implementation that currently presents Baseline information. Confirm how browser support data is assembled, then restore the browser-version section alongside Baseline information, including for newly added properties.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, typescript
Domain
frontend, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.