Closed Bug 264098 Opened 20 years ago Closed 17 years ago

When adding Developer Tools to a previous install, DOM inspector fails to operate correctly.

Categories

(Firefox :: Installer, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jaraco, Unassigned)

Details

(Whiteboard: CLOSEME 07/05)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

DOM Inspector behaves incorrectly if Developer Tools was not selected during the
initial installation of Firefox.  In particular, the DOM Nodes section does not
display anything at all.  The "Find Nodes..." and "Select Element by Click"
functions did nothing.
A complete uninstall and reinstall with the Developer tools fixes the problem.

Reproducible: Always
Steps to Reproduce:
1. Install Firefox without the developer tools.
2. Install Firefox over original installation with the developer tools.

Actual Results:  
DOM inspector behaves incorrectly.  Some functions are unavailable.

Expected Results:  
All functions should be available if the DOM Inspector was installed.

Problem occurred on two machines, each running Windows XP SP2.
I have also reproduced this bug on a Windows XP SP2 machine.

The particular behaviour is that I cannot see the DOM nodes.  Stylesheets and
javascript objects work fine, but dom nodes seems to be inactive, as even when I
select it, the text to the side stays as "javascript object" if that's what I
had selected previously.
Assignee: bugs → nobody
QA Contact: bugzilla → installer
Version: unspecified → 1.0 Branch
Whiteboard: CLOSEME 07/05
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Installing Firefox 2.0.0.4 in a Windows XP SP2 machine no longer seems to exhibit this behavior.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.