Update HTML highlighting & IntelliSense

[dstorey]

HTML syntax highlighting and IntelliSense in CSS were out of sync and somewhat outdated.

Removed deprecated:

• acronym
• big
• strike
• tt
• frame
• frameset
• noframes
• eventsource

Added from HTML5:

• bdo
• data
• embed
• main (also added to the HTML IntelliSense)
• rb, rp, rt, rtc, ruby
• s
• source
• template
• track
• u
• wbr

Added from HTML5.1 (less stable spec but many have 1 or 2 implementations)

• svg (also added to CSS IntelliSense)
• menuitem

Also updated the CSS transition snippet, which uses the wrong order and has -o- prefix that has not been needed for a long time.

[msftclas]

Hi @dstorey, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (David Storey). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

[dstorey]

…the HTML elements in CSS IntelliSense should now be consistent with what is syntax highlighted via the TextMate file. There are things that could arguably be removed, like that was dropped from the WhatWG spec (and Edge will not implement, and Chrome want to deprecate) and

, which was dropped from the W3C version of the spec.

The HTML IntelliSense also needs double checked. I added the

element as that was bugging me, but as it is not in alphabetical order, it will take a while to cross check against the 2 other HTML lists and the spec. It would be nice eventually to only have one list of elements rather than 3 that need to be kept in sync.

[dstorey]

Decided to update the HTML auto-complete/IntelliSense file while I was at it. It should be now in sync with the CSS auto-complete for HTML elements, and have all the correct attributes per the latest HTML5.1 spec and WHATWG Living standard, along with the valid enum and boolean values for those

[aeschli]

@dstorey Really nice, thanks so much. One thing:
CSS.plist is from https://github.com/textmate/css.tmbundle. Would you mind also make a pull request there, so we stay in sync? I can also do it, just let me know.

[aeschli]

You mentioned the 3 files we have to keep in sync.
The tokenizer will always be separate as we want to use the text mate tokenizer from the community and don't want to branch off.
Code reuse between languages is tricky. For runtime, each language is packaged separately. If we reference the htmlTags file from CSS that whole file and dependencies end up in the CSS package, increasing the memory foot print of CSS. We would have to break it up in small pieces and make sure it stays useful for both HTML and CSS.
Eventually CSS and HTML will become real VS code extensions. Right now they are implemented in an old style and are located in our VSCode repo. They would each go in their own git repo. Code sharing would then have to be done through a common node module that provides the shared code.
So I think for now I'd rather avoid that and live with two separate tables.

[dstorey]

@aeschli sure, I can look at making a PR to TextMate. I did a similar update to Atom when it was new, which I guess wasn't pushed back to TextMate as this version was further out of date than that version. I guess there are a fair few of these files of different vintages across the different editors that use TextMate plists.

[aeschli]

@dstorey Lets submit the pull request and see if they take it. The experiences so far have been good, with a quick turnaround. Our goal is to avoid a branch as long as we can, so either side can profit from bug fixes.