See the attached file or http://paste.kde.org/775436/ Reproducible: Always Steps to Reproduce: 1. Save the attached file as file.js 2. Open it. 3. Check the syntax highlight. Actual Results: The syntax highlight is broken. Expected Results: The syntax highlight should not be broken. See the attached images for real-world examples. Workaround: revert 13eee5d37687dbbe2ed1195168e423695551207c. I am aware that 13eee5d37687dbbe2ed1195168e423695551207c fixes other issues, but it introduces heavier problems than it solved. I don't know how to fix that in a good manner, but probably there should be a better solution than just reverting the commit.
Created attachment 80837 [details] Testcase
Created attachment 80838 [details] Screenshot of the bug (on the testcase)
Created attachment 80840 [details] Screenshot of the bug (on the Leaflet source code).
This bug is valid for kate 3.10.80 (KDE SC 4.10.80) and kate 3.10.90 (KDE SC 4.10.90).
I can confirm this bug. What was the problem with spaces being identified as part of member names? Did that cause problems somewhere else?
Then it should be reverted. A fix then can still be provided.
Does anybody have a quick solution or shall I revert?
somebody broke it anyway, so go ahead and revert. but we have that space problem. i filed a bug for it: https://bugs.kde.org/show_bug.cgi?id=322577
fixed this already *** This bug has been marked as a duplicate of bug 321859 ***
why would you think that i’d mention that i created a duplicate bug while being aware that this bug exists? i filed bug 322577 because the reverting is just wrong in another way. please look at the test case in bug 322577 to see what should work simultaneously.