(why the issue was filed, steps to reproduce the problem, etc.)
Behat's greedy matching means that the sitewide search seems to get found before the searches on all other pages, which makes us write extra step definitions each time that conflict arises. That's extra work we don't probably want to maintain.
(description of the proposed solution, the rationale behind it, and workarounds for people who cannot use the patch)
I have implemented a step to allow us to target the sitewide search
When I search sitewide for ""
I'm hoping that we could write a step that looks something like:
When I enter the term "" and press "" that excludes a match against the sitewide search's id tag.
If we include a comment beneath the step definition explaining the intent of the step it will appear with the -di output so people will undertand what it's intended for.
- Update #1681444: Problem with the submit button existing more than once in the same page. (search.feature project_search.feature) when this is implemented (and grep for the word search in the feature files)
- Remove the more static step definitions