Chore: Remove blocking status and mapping columns from cookies table #748
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.
Description
Remove "Blocking Status" and "Mapping" columns from cookies table as they are no longer being used and were be removed in the next version
Relevant Technical Choices
useCookieListing
hook.OrphanedUnMappedInfoDisplay
component which was used for mapping column.message.json
files.Testing Instructions
Additional Information:
They were originally added because of the mixed API usage. Some cookies that CDP was able to catch (outbound blocked request cookies) could not be caught by the
webRequest API
.Due to issues with CDP, we were unsure if the blocking status and mapping problem would resolve. In our testing, we didn't find any blocked cookies. However, since we and QA test a wide variety of websites, we decided to keep these columns for v0.9 in case anyone reports issues with blocking status and cookie mapping information.
Screenshot/Screencast
Checklist
- [ ] This code is covered by unit tests to verify that it works as intended.NAFixes #