Recently I'm trying to explore gecko engine also, it seems a seperately
self-maintained codebase of render engine is what many guys want, but it
seems it's very hard to extract the codes from the firefox / mozilla
codebase yet (At least I didn't find a good solution yet. According to the
document,
ering? Because in some
research work, a fast html parser with viusal information (position of
element) is very useful, especially in large number of documents. Thanks!
--
View this message in context:
http://www.nabble.com/Dom-with-Rendering-info-for-HTML-pages-tf1885868.html#a5551663
Sent fro
john alden wrote:
Hi
I understood that the patch mentioned by you will be useful to get what i want. Thank you for the info.
I have been trying to understand the various components of mozilla code base. The code base is huge and i got lost in it. I dont know where to start from. Can you p
Hi
I understood that the patch mentioned by you will be useful to get what i
want. Thank you for the info.
I have been trying to understand the various components of mozilla code base.
The code base is huge and i got lost in it. I dont know where to start from.
Can you please give me po
john alden wrote:
What sort of rendering information do you want?
Given an element in DOM, i want information about its layout. For example, for a given text element i want co-ordinates of the rectangle in which the text element is rendered. The co-ordinates can be top,left,bottom,right ( as me
> What sort of rendering information do you want?
Given an element in DOM, i want information about its layout. For example, for
a given text element i want co-ordinates of the rectangle in which the text
element is rendered. The co-ordinates can be top,left,bottom,right ( as
mentioned in the
john alden wrote:
> 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
>
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,
john alden 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 l
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 ther
10 matches
Mail list logo
