276270 - Receive Javascript alert "no bundle" whenever I click View Page Source

Status: RESOLVED INVALID

(Core Graveyard :: View Source, defect)

Description

[Michael Dowden]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217

Whenever I view page source (regardless of what page or what website) I get a
Javascript alert that reads "no bundle."  This means that I must click OK to
actually see the source code.  Basically this is just an annoyance but, since as
a web developer I use this feature several times a day, it gets rather old
having to go through the extra step each and every time.

I am not sure what is causing this alert, but is there any it can be removed?  I
have had this problem ever since 1.7.2 (perhaps since 1.7.1, but I don't
remember for sure), but did NOT have the problem in 1.7.  I am currently using
1.7.5 and still having the problem.  The problem started immediately after
installing the new version (Again, I don't remember for sure if it started with
1.7.1 or 1.7.2.  I know for sure that it occurs in 1.7.2, 1.7.3, and 1.7.5).

Reproducible: Always

Steps to Reproduce:
1. Load a page
2. Click View Page Source
3.

Actual Results:  
Received JavaScript alert reading "no bundle."  After clicking okay, I get the
Source window.

Expected Results:  
I should get the Source window without the alert.

This bug occurs with every theme I have used, including the standard Modern
theme.  In case it helps, I have the following extensions installed:

Checky 2.2
Extension Uninstaller 0.2.1
Extension Uninstaller API
IE View 0.81
Image Zoom
Themer
undoclosetab

I am pretty sure that I had some but not all of these extensions installed
before I started experiencing the problem.

Comment 1

[Doron Rosenberg (IBM)]

can you create a new profile and see if you can reproduce?  It works fine for me
on 1.7.5 and the 1.7 branch.

Comment 2

[Michael Dowden]

Okay, I gave that a try and the new profile is unaffected and works fine.  Never
thought to try that one.  My original profile is still affected, however.  Is
there any way to repair the primary profile?

Comment 3

[Doron Rosenberg (IBM)]

It is probably an extension that is causing this.