Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Selector change breaks column replacement in Filtering class
The
openFilterselector changed from'[id="pm-table-column-{col}"] button'(with{col}placeholder) to'[class="pm-table-ellipsis-column"] [class="pm-table-column-header"]'(no placeholder). TheFilteringclass inpages/filtering.jsstill callsselectors.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 thecolumnparameter, causing filtering to target the wrong elements or behave unexpectedly.