Hi
Thanks for your reply Robert.
But what i want something which is slightly different from what is mentioned
there. As far as i understand, whats mentioned in the bug you mentioned below
is a way to access rendering information from JavaScript for a particular node.
What i need is, I wanted to build a Document Object Model (DOM) which has
rendering information for its nodes. I wanted to use the Gecko layout engine
and the Mozilla's DOM to build an interface to get what i want. Once i have the
DOM with rendering information, i want to serialize the dom ( store the dom as
xml ). Put in a simple way, if i give a url as input, i need a DOM which has
rendering information for its nodes as output. Then later i will serialize the
data on my own.
If any one can help me how to approach the above problem, it would be really
great :)
Thanks,
John Alden.
> Robert O'Callahan wrote:
>
> One way would be to apply the patch in
> https://bugzilla.mozilla.org/show_bug.cgi?id=174397. Then you can
> traverse the DOM calling getClientRects on each element.
>
> Rob
john alden <[EMAIL PROTECTED]> wrote:
Hi
I am new to Mozilla. I am interested in knowing how the rendering engine
works.
I want to traverse the DOM which has rendering information of each of its
node given its environment is fixed ( if the Window size, resolution etc is
fixed ). I am looking at only HTML pages. Is there any way in which i can use
Gecko to get what i need ? Any suggestions (or sample code) would be great.
Essentially i want to traverse the html page in the order it is displayed to
the user.
Thanks,
John Alden
---------------------------------
How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
