Vapir link.text didn't return the right text for the link

[xul...@yahoo.com]

Hi Ethan,

When I switch to use vapir, my previous test cases are failed due to
the link.text returns extra "\n" characters.

the following is the compare of vapir and firewatir.
FireWatir returns what I need.
irb(main):009:0> ie_offer.link(:href, /.*whatever.mpl*./).text
=> "linkstring"

Vapir returns extra "\n".

irb(main):006:0> ie_offer.link(:href, /.*whatever.mpl*./).text
=> "\n \n linkstring\n "

I haven't try other complicate test cases yet, but I suspect some more
inconsistency with firewatir.
Do you have plan to release new version lately?
Since I love the new features of vapir, but I can't change too much to
meet the vapir favor so far.

Thanks,

[Ethan]

making the text that is returned (and matched when specifying) consistent cross-browser is currently around the top of my list of priorities. 

it's not possible to make it completely the same, because IE and firefox just don't give enough information to return results that are entirely consistent. I did not like firewatir's approach because it was causing inconsistencies (just within firewatir, even ignoring IE), and I had to remove it and just return exactly what firefox does, but unfortunately I didn't come up with a better solution so that it would be consistent with IE. I have a partial solution implemented, which I hope to complete very soon, possibly this week, and get a release out soon after that.