"in" is a Javascript keyword, eg for (var p in obj) ...

jjb

On Dec 6, 1:28 pm, Patrick <[email protected]> wrote:
> Through trial and error I found what was crashing the compiler.
>
> var in
>
> Apparently it overrides some global variable in (e.g. input stream)
>
> I changed it to
>
> var inches
>
> and added the document object selection and got the script to show,
> debug and work.
>
> Next step is to embed everything within an object.
>
> Patrick
>
> On Dec 5, 9:28 am, John J Barton <[email protected]> wrote:
>
> > Please try Firebug 1.5b5,http://getfirebug.com/releases/firebug/1.5X.
> > If you still have a problem, post a complete test case 
> > tohttp://code.google.com/p/fbug/issues/listandI'll fix it.
>
> > jjb
>
> > On Dec 4, 11:49 pm, Patrick <[email protected]> wrote:
>
> > > I got the latest version of Firebug and installed in on Firefox 3.5.5
> > > browser.
>
> > > I have a Javascript file which shows up as an enabled script so long
> > > as I don't have the following function in the script file.
>
> > > function onChangeUnitsOfLength() {
> > >         var hUnits = getElementsById("hUnits");
> > >         var m = getElementById("m");
> > >         var in = getElementById("in");
> > >         var ft = getElementById("ft");
>
> > >         switch(hUnits.value) {
> > >         case 0:
> > >                 m.style.zIndex= "-1";
> > >                 in.style.zIndex="0";
> > >                 ft.style.display="inline";
> > >                 break;
> > >         case 1:
> > >                 m.style.zIndex="-1";
> > >                 ft.style.display="none";
> > >                 in.style.zIndex="0";
> > >                 break;
> > >         case 2:
> > >                 m.style.zIndex="0";
> > >                 ft.style.display="none";
> > >                 in.style.zIndex="-1";
> > >                 break;
> > >         default:
> > >         };
>
> > > };
>
> > > When I add this function to the file, my file no longer shows in the
> > > drop down menu and there is no code where I can set breakpoints.  I
> > > don't think an error in the code should break the debugger but it
> > > does.  It would be nice if there were some way to spot errors in the
> > > code before you try to evaluate it.
>
>

--

You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en.


Reply via email to