This morning I realized how stupid that was : i'm creating my Tree from the HTML content only, while the object position can be influenced by the Javascript (And other stuff? And something that manages the display layout i guess), which WWW::Mechanize::Firefox "takes into account" (simple words for beginner understanding).
I read it several times, i knew it but forgot it while doing this first test. I guess i hoped there could be a (bijective) correspondence between the two. And i made this mistake also because i was doing this first test on an example where there is no Javascript at all.
Next step for me : learn about XPath.
From what i remember it looks fairly much like a Tree. So i guess i could use similar algorithms.
Any major difference ?
Thanks again for helping me understand :o)
Now i know where to look, which makes a big difference.
In reply to Re^8: WWW::Mechanize - how to get the position of an element on my screen?
by mascip
in thread WWW::Mechanize - how to get the position of an element on my screen?
by mascip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |