How can i locate the particular file using firebug

[unoto]

Hello everyone

How can I locate the file using firebug?

I have been trying to locate the file.. but I am not finding the
particular div either in the css file or php or html ..

waiting for the reply..

thank you

[John J Barton]

On Mar 28, 10:33 pm, unoto <unokin...@gmail.com> wrote:
> Hello everyone
>
> How can I locate the file using firebug?

I've hidden the file inside the cake. You will find it when you eat a
slice.

>
> I have been trying to locate the file.. but I am not finding the
> particular div either in the css file or php or html ..

Maybe your div was added by JavaScript?

jjb

[ColinFine]

On Mar 29, 3:27 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
> On Mar 28, 10:33 pm, unoto <unokin...@gmail.com> wrote:
>
> > Hello everyone
>
> > How can I locate the file using firebug?
>
> I've hidden the file inside the cake. You will find it when you eat a
> slice.
>

John, that is unkind, as a reply to a user whose language is probably
not English.
Unoto: John's reply is a joke, playing on a different meaning of the
word "file".

>
>
> > I have been trying to locate the file.. but I am not finding the
> > particular div either in the css file or php or html ..
>
> Maybe your div was added by JavaScript?
>

That is a more helpful reply.

[unoto kinimi]

thanks mate

so can i edit the div generated by javascript..

A help in this matter would be grateful 

[John J Barton]

On Mar 30, 1:32 am, ColinFine <colin.f...@pace.com> wrote:
> On Mar 29, 3:27 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:> On Mar 28, 10:33 pm, unoto <unokin...@gmail.com> wrote:
>
> > > Hello everyone
>
> > > How can I locate the file using firebug?
>
> > I've hidden the file inside the cake. You will find it when you eat a
> > slice.
>
> John, that is unkind, as a reply to a user whose language is probably
> not English.

Of course you are correct. My frustration spilled over from the bug
list where it seems no matter what kind of instructions we put in the
page we still get reports that are equivalent to "Hey something is
broken". Then we have to go though a long exchange to learn very
little then (typically) it will come out that the problem wasn't in
Firebug at all.


jjb

[ColinFine]

Since you haven't given us *any* specific information about your
problem, it is hard to advise you (which is why John got frustrated
and gave you that unhelpful answer), but:

I'm guessing that you are saying that there is a div in your DOM and
you want to know where it comes from.

John's suggestion that it is created by Javascript is possible, but do
you have reason to think that is the case?

I'm guessing that the div is there in the HTML sent from your server,
and you are expecting Firebug to help you find out what file on the
server it comes from. I may be wrong, but when you don't provide us
*any* useful information, all we can do is guess.

If that is the case, you need to understand that Firebug, and Firefox,
and the entire system you are running on your client *cannot* know
anything at all about the files on your server. All that they know is
what the server sent back in the HTTP response when they sent an HTTP
request (the URL)

Often URL's have what look like filenames in them, and often when a
server receives a request with a filename in it, it will in fact serve
a file with that name: but servers are entitled to do anything else
they like in order to fulfil the request.

If you are seeing the div in the HTML panel of FB, it is there in your
DOM. Normally, it will have been provided as part of a GET or POST,
and Firebug will tell you at the top of the panel which URL this came
as the response to. (If you think it might not have been there when
the page loaded - John's suggestion - then it might be an idea to look
at the original source of the page, either by putting a breakpoint
somewhere in your Javascript before it does anything, or perhaps by
installing the WebDeveloper extension and picking ViewSource. (There
may be a way to get the original source in FB, I don't know).

If you find that your div is there in the original source, then you
don't need to worry about Javascript, and you need to find out where
your server gets the data in its request.

If it is not in the original source, then it is generated dynamically
in your page, probably by Javascript, and you will need to examine
your Javscript, and perhaps start debugging it with messages or
breakpoints.