Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Insert warning on deprecated / obsolete HTML Elements #30

Closed
lannonbr opened this issue Jul 28, 2018 · 2 comments
Closed

Insert warning on deprecated / obsolete HTML Elements #30

lannonbr opened this issue Jul 28, 2018 · 2 comments
Assignees
@octref @aeschli
Milestone
Backlog

Comments

@lannonbr
Copy link

As a feature that could be implemented after #22, It would be neat to either display a warning / error on html elements which are deprecated (blink, marquee, etc.).

In MDN's browser-compat-data repo, html elements have a deprecated property on them (For instance, here on the blink tag, so if the language server switches to use MDN's data, this could be a fairly quick feature to implement.
@aeschli aeschli added this to the Backlog milestone Sep 18, 2018
@connorshea connorshea mentioned this issue Oct 2, 2018
Closed
@octref octref mentioned this issue Nov 8, 2018
Closed
@octref
Copy link
Contributor

octref commented Jan 14, 2019

Currently we only have this inside our code:

image

But MDN does have relevant info, for example https://developer.mozilla.org/en-US/docs/Web/HTML/Element/menuitem. After finishing up #44 I can look into this.

@octref octref self-assigned this Jan 14, 2019
octref added a commit that referenced this issue Jan 15, 2019
@octref
Refactor custom data support.
4773ebb 
Changes:

- Feature: HTML attribute completion documentation
- Rename: tagProvider -> dataProvider
- API: Now in sync with CSS LS API
- HTMLTagSpecification converted to serializable plain data structure
so does attributes and attribute values
- Remove Angular1/Ionic1 support
- Remove i18n for HTML tags, and manage them in a plain JSON-like file because
  - We don't have i18n support in LSP yet
  - There's no translation yet
  - The JSON-like file is typed and can be easily mainaintaed
  - We'll start pulling data from W3C HTML spec and MDN to do features
  such as short descriptions, browser support table adn syntax. Such
  plain JSON-like files are easy to auto-generate.
  - Unblocks #12, #30, #44

Fixes:

- Fix microsoft/vscode#2784
- Part of microsoft/vscode#63955 (no CompletionItem.documentation for attr value yet)
octref added a commit that referenced this issue Jan 15, 2019
@octref
Refactor custom data support.
c3b860b 
Changes:

- Feature: HTML attribute completion documentation
- Rename: tagProvider -> dataProvider
- API: Now in sync with CSS LS API
- HTMLTagSpecification converted to serializable plain data structure
so does attributes and attribute values
- Remove Angular1/Ionic1 support
- Remove i18n for HTML tags, and manage them in a plain JSON-like file because
  - We don't have i18n support in LSP yet
  - There's no translation yet
  - The JSON-like file is typed and can be easily mainaintaed
  - We'll start pulling data from W3C HTML spec and MDN to do features
  such as short descriptions, browser support table adn syntax. Such
  plain JSON-like files are easy to auto-generate.
  - Unblocks #12, #30, #44

Fixes:

- Fix microsoft/vscode#2784
- Part of microsoft/vscode#63955 (no CompletionItem.documentation for attr value yet)
@octref octref mentioned this issue Jan 15, 2019
Merged
@aeschli
Copy link
Contributor

aeschli commented Nov 11, 2020

Validation is not planed.

@aeschli aeschli closed this as completed Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@octref octref

@aeschli aeschli

Labels
None yet
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@lannonbr @octref @aeschli