-
Notifications
You must be signed in to change notification settings - Fork 98
Tag matching doesn't work in HTML with tree-sitter enabled #355
Comments
Thanks for the report - I think this is an issue with tree-sitter, do you have tree-sitter enabled @oueryemchi ( Also, what version of Atom are you running ( |
Indeed! you're the man! that was the culprit and you saved the day ;) Thanks much! For info sake: I am on Win 10 - 64Bit (updated to latest) and Atom version is 1.29.0 |
Going to go ahead and re-open just to confirm this is fixed - /cc @maxbrunsfeld @queerviolet. @maxbrunsfeld we talked about this a bit ago and I think you mentioned this will be fixed and that I should ping you in an issue for the behavior just for tracking? |
Just to note on this that it works for me in normal HTML documents but not in documents that don't have an opening We use HTML includes where I work and the includes are just blocks of HTML. With the tree sitting enabled tag matching doesn't work on these includes, but does on any normal HTML document. This is in Atom v1.33.0-beta1. |
This is also an issue for jsx. |
Ok, sorry about this everyone. The fix will ship in Atom 1.33 and 1.34 beta. |
I'm having the bizarre problem where one HTML file with |
Edit by @rsese to add issue template details
Prerequisites
Description
Bracket matching in HTML doesn't work with tree-sitter enabled.
Steps to Reproduce
Settings > Core > Use Tree Sitter Parsers
test.html
with thehtml
snippet content:<body>
tag.Expected behavior: [What you expect to happen]
Expect the
<\body>
tag to be highlighted.Actual behavior: [What actually happens]
The
<\body>
tag isn't highlighted.Reproduces how often: [What percentage of the time does it reproduce?]
100%
Versions
macOS 10.12.6
Additional Information
If you disable tree-sitter, the tag matching works.
always worked in all files. after updating Atom and packages 2 days ago (done on 2d of August 2018), Matcher stopped working in plain HTML files.
I disabled all packages and left on the core ones, still not working..
The text was updated successfully, but these errors were encountered: