Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#23399 closed defect (worksforme)

After I updated TBB from 7.0.4 to 7.0.5, the httpseverywhere extension shows up blank

Reported by: Dbryrtfbcbhgf Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

After I updated TBB from 7.0.4 to 7.0.5, the httpseverywhere extension shows up blank when I click on it.

Child Tickets

Attachments (2)

bug.png (272.5 KB) - added by Dbryrtfbcbhgf 2 years ago.
Photo of the bug
bug 1.png (72.6 KB) - added by Dbryrtfbcbhgf 2 years ago.

Download all attachments as: .zip

Change History (8)

Changed 2 years ago by Dbryrtfbcbhgf

Attachment: bug.png added

Photo of the bug

comment:1 Changed 2 years ago by Dbryrtfbcbhgf

Deleting TBB and re-downloading it fixes the issue, but all users that use the builtin updater might be effected by this bug.

comment:2 Changed 2 years ago by boklm

Which security level are you using?

My Tor Browser updated from 7.0.4 does not have this issue.

comment:3 in reply to:  2 Changed 2 years ago by Dbryrtfbcbhgf

Replying to boklm:

Which security level are you using?

My Tor Browser updated from 7.0.4 does not have this issue.

High.

Last edited 2 years ago by Dbryrtfbcbhgf (previous) (diff)

Changed 2 years ago by Dbryrtfbcbhgf

Attachment: bug 1.png added

comment:4 in reply to:  2 Changed 2 years ago by Dbryrtfbcbhgf

Replying to boklm:

Which security level are you using?

My Tor Browser updated from 7.0.4 does not have this issue.

I found what was causing the bug, I went into about:config and set javascript-enabled to false before I updated, after the update settings javascript-enabled to false causes the bug to occur.

comment:5 Changed 2 years ago by gk

Resolution: worksforme
Status: newclosed

So this is causes by an error in your config and not really a bug, right?

comment:6 in reply to:  5 Changed 2 years ago by Dbryrtfbcbhgf

Replying to gk:

So this is causes by an error in your config and not really a bug, right?

It looks like it.

Note: See TracTickets for help on using tickets.