Actually, it appears the problem is a bit more complicated. I am calling a function on completion of an upload from the uploadify jquery component. In that function I am changing the value of a hidden input control, and that seems to confuse firebug. It might be because the javascript function is executed within the context of a flash callout that is causing the disconnect between what firebug sees as the value in the DOM pane and the HTML pane. Odd that setting the value to a non-blank value will cause firebug to keep them in sync however.
On Sep 17, 1:23 pm, Robert McKee <[email protected]> wrote: > I have some javascript code that changes some hidden input fields, and > when I used firebug to look at the html for them, all the input fields > except for one had the value field changed. The one that did not > update initially started as a blank field. When I changed the page > to initially set the field to "0", then that field would update as > well in the HTML pane. Note that the DOM inspector always showed the > value to change, even when initially blank. > > Such as: > <input type="hidden" id="field1" value="" /> > <input type="hidden" id="field2" value="0" /> > <script> > $("#field1").attr("value","1"); > $("#field2").attr("value","1"); > </script> > > This is a very simplified example that I hadn't really tested, but at > the end, in the HTML pane of firebug, field1 will still show value="" > while field2 will now show value="1". I would have expected that > either the HTML would not update at all, or both would update, but not > one and not the other. Of course, I would prefer both update. > > This is with firebug 1.5.4. -- 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.
