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
Fix for #8034 - smart search fail on $ #8097
Conversation
the problem was that |
|
I haven't checked the code, but I would think that all "punctuation" characters will be stripped. Same for the indexer. That would be expected behaviour. |
@chrisdavenport Not so sure we can consider $ , € etc ..... a punctuation character |
For the kind of websites I normally work with I wouldn't want these characters cluttering up the index. However, I can imagine that there would be occasions where some websites might want to retain them. I would suggest that this needs to be configurable because it depends on the particular application. It's rather like how we currently have a list of "stop words" that are not indexed. I think we should have a configurable list of "stop characters" that are discarded and/or regarded as delimiters. I'd be happy to review a PR for that feature. |
👍 p.s. |
I have tested this item ✅ successfully on f3f7e62 The consequential issue reported by @alikon should be the subject of a separate PR along the lines I suggested. This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8097. |
I have tested this item ✅ successfully on f3f7e62 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8097. |
RTC. Thanks This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8097. |
Thank you @Fedik and testers! |
this fix for #8034
the problem was that
$
is striped and the highlighter script tries to highlight the emptiness, that cause high resource usage by highlight.jsfor testing please look the description in related issue 😉
Steps to reproduce the issue
Expected result
some search results
Actual result
javascript loop resulting in massive memory leak and eventual browser crash
System information (as much as possible)
browser = firefox
OS = Win 10
Additional comments