When clicking on a word not otherwise recognized as a symbol, the non-word character (whitespace or punctuation) before the word is included in the popup "Search for the substring", and will be included in the search if that option is selected. [An example](https://searchfox.org/mozilla-central/rev/7fd1c1c34923ece7ad8c822bee062dd0491d64dc/browser/base/content/safeMode.js#25), click `MOZ_RESET_PROFILE_RESTART`. I think this is a regression as I use this functionality pretty heavily and only noticed it today. It think it was caused [by this commit](https://github.com/mozsearch/mozsearch/blame/a38b66573ea9c514af00fa545851c5894be57eb7/static/js/context-menu.js), [this loop] stops searching backwards when it finds a non-word char, but `start` is left pointing there (or possibly at -1). `start += 1` would likely fix this.
Bug 1634100 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When clicking on a word not otherwise recognized as a symbol, the non-word character (whitespace or punctuation) before the word is included in the popup "Search for the substring", and will be included in the search if that option is selected. [An example](https://searchfox.org/mozilla-central/rev/7fd1c1c34923ece7ad8c822bee062dd0491d64dc/browser/base/content/safeMode.js#25), click `MOZ_RESET_PROFILE_RESTART`. I think this is a regression as I use this functionality pretty heavily and only noticed it today. It think it was caused [by this commit](https://github.com/mozsearch/mozsearch/blame/a38b66573ea9c514af00fa545851c5894be57eb7/static/js/context-menu.js), [this loop](https://github.com/mozsearch/mozsearch/blob/b906106ce547fc6bca13ea5e2c0dc0550eb44375/static/js/context-menu.js#L221-L223) stops searching backwards when it finds a non-word char, but `start` is left pointing there (or possibly at -1). `start += 1` would likely fix this.