[CRX] Fix feature detect of DNR responseHeaders option
Fix regression from #18711. `urlFilter` is a key of `condition`, not of the `rule`. Consequently, the feature detection method failed to detect the availability of the feature in Chrome 128+.
This commit is contained in:
parent
66ed4b9e25
commit
a91ba11185
@ -227,8 +227,10 @@ async function isHeaderConditionSupported() {
|
||||
addRules: [
|
||||
{
|
||||
id: ruleId,
|
||||
urlFilter: "|does_not_match_anything",
|
||||
condition: { responseHeaders: [{ header: "whatever" }] },
|
||||
condition: {
|
||||
responseHeaders: [{ header: "whatever" }],
|
||||
urlFilter: "|does_not_match_anything",
|
||||
},
|
||||
action: { type: "block" },
|
||||
},
|
||||
],
|
||||
@ -244,8 +246,10 @@ async function isHeaderConditionSupported() {
|
||||
addRules: [
|
||||
{
|
||||
id: ruleId,
|
||||
urlFilter: "|does_not_match_anything",
|
||||
condition: { responseHeaders: [] },
|
||||
condition: {
|
||||
responseHeaders: [],
|
||||
urlFilter: "|does_not_match_anything",
|
||||
},
|
||||
action: { type: "block" },
|
||||
},
|
||||
],
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user