-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
[CLOSED] Code hints broken for rest of line after HTML entity #3139
Comments
Comment by peterflynn
In addition to a fix, we should add a couple of unit tests in this area. |
Comment by peterflynn I would question whether SpecialCharHints should have anything other than "&" in its trigger keys. In other words, unless implicitChar is null or "&", hasHints() should always return false. This also avoids the added compute cost of calling _getQuery() on virtually every keystroke while editing HTML. |
Comment by WebsiteDeveloper the problem is, that removing all the trigger keys except "&" does show hints when "&" is typed but when one types "&a" then no hints are displayed anymore. I'll look into it and also add a few unit tests. |
Comment by peterflynn I'm seeing a few other problems with this extension. Let me know if you prefer I break these out into separate bugs:
|
Comment by WebsiteDeveloper please split those up i already have a fix for the cases mentioned in this bug. |
Comment by pthiess Reviewed |
Comment by redmunds FBNC back to |
Comment by peterflynn
Feel free to reassign back to me if you're overbooked though |
Comment by RaymondLim Fix verified. |
Issue by peterflynn
Thursday Apr 04, 2013 at 07:18 GMT
Originally opened as adobe/brackets#3339
Start with the following code:
Result:
2 - code hints pop up listing all HTML entities
3 - entity hints remain visible; there is no sign of the list being filtered down at all
4 - same entity hints pop up again
5 - no code hints appear
6 - same entity hints pop up again
Expected:
2, 3, 4 - no code hints
5, 6 - HTML tag code hints pop up
The text was updated successfully, but these errors were encountered: