Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#8998 closed defect (fixed)

wouldMatch is not defined while browsing

Reported by: bastik Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version: HTTPS-E 3.2.1
Severity: Keywords:
Cc: Actual Points:
Parent ID: #9480 Points:
Reviewer: Sponsor:


While I'm logged in (into and performing tasks like commenting on issues the error log spits out several errors.

Time stamp: 30.05.2013 !13:39:00
Error: wouldMatch is not defined
Source: chrome://https-everywhere/content/code/HTTPSRules.js
Line: 661
(translated the German strings by myself)

Line 661 contains

return wouldMatch(test_uri, null);

HTTPS Everywhere is actually 3.2.2 (but I can't select it here)

Firefox is German 21 (32bit) on Windows 7 (64bit)

Child Tickets

Change History (2)

comment:1 Changed 7 years ago by zyan

Resolution: fixed
Status: newclosed

This is fixed in master and is in the process of getting merged.

comment:2 Changed 7 years ago by zyan

Parent ID: #9480
Note: See TracTickets for help on using tickets.