Continue rules processing after first disabled one
With the Manifest V3 migration in 619b1197, the logic to process rules
used a filter() with disabled rules using an empty return to be filtered
out. The refactoring removed the filter but kept the return which means
the first disabled rule causes an early return and no other rule is
processed.
Since the rules are now processed in a loop, a disabled rule should
cause a continuation of the next iteration.
Change-Id: Ieef2a3c4af2bc43b39ec71682483cb9144327f87
diff --git a/src/content_script.ts b/src/content_script.ts
index 486c897..3d5478f 100644
--- a/src/content_script.ts
+++ b/src/content_script.ts
@@ -125,7 +125,7 @@
const rules = await storage.getRules();
for (const rule of rules) {
- if (rule.disabled) return;
+ if (rule.disabled) continue;
if (rule.operator === Operator.INJECT_HTML_CODE) {
const el = document.createElement('div');
el.innerHTML = rule.destination;
