Conversation
There was a problem hiding this comment.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| filterFooterBtns: '[class="pm-filter-form"] fieldset', | ||
| tableRequest: '[class="pm-table-container"]', | ||
| /*new filteringV1 | ||
| //new filteringV1 |
There was a problem hiding this comment.
Bug: Selector change breaks column replacement in Filtering class
The openFilter selector changed from '[id="pm-table-column-{col}"] button' (with {col} placeholder) to '[class="pm-table-ellipsis-column"] [class="pm-table-column-header"]' (no placeholder). The Filtering class in pages/filtering.js still calls selectors.openFilter.replace("{col}", column), but since the new selector lacks {col}, the replacement has no effect. All columns will use the identical selector regardless of the column parameter, causing filtering to target the wrong elements or behave unexpectedly.
Note
Replaces legacy filtering selectors with the new filteringV1 selectors and comments out the old entries.
selectors/filtering.js):openFilterandfilterFormselectors.openFilter(ellipsis column),threeDots,modalFilter,filterForm,sortButton.optionFilter,valueFilter,removeButtonModal,addNewFilterButton.Written by Cursor Bugbot for commit cb56e0e. This will update automatically on new commits. Configure here.