On Jul 26, 10:20 pm, teresa <[email protected]> wrote:
>  I just started to use firebub,. I have seen a few video tutorials
> where they show how you click on an element using FB and it will
> highlight the code and tell you the page where you will find this
> element code to make changes.. When I click on an element, say,  a
> header, I do see the code on the left side  (i believe it's HTML), but
> the right side does not match the left side. The right side will tell
> me I can find that element code in such and such a page, but when I go
> there, that page is totally different, and the code is not there. So I
> am not able to find any code using FB.
>
I'm not entirely clear what you mean, but I think you may be under a
(very common) misconception.

Firebug will show you where in the _data received by the browser_ a
particular thing occurs - whether a DOM element, some Javascript, a
CSS rule.

If that item happens to be part of a server response which was more or
less a literal file from the server (as CSS and Javascript often are,
though not always), then Firebug may be able to point you at the file
on the server that contains it.
But if the server's response was generated (eg by a CGI program, or
some PHP) then there may be no file on the server which contains the
data you are looking for, and in any case Firebug cannot do much to
help you find where it comes from.

If I have misunderstood and this is not the problem, I apologise.
Perhaps you would like to make the issue a bit clearer.



>  I search for relevant words in pages to find the code ( though that
> defeats the purpose of FB), but I can never find the page where the
> code is, even though FB tells me to go to such and such page to find
> the code. It's not there. It's not even the right page.
>
>   Am I missing something? perhaps some kind of setting?
>
> thanks!!!

-- 
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