Chris McMahon wrote: > Quoting from the Selenium reference: > storeText ( locator, variableName ) > Gets the text of an element. This works for any element that > contains text. This command uses either the textContent (Mozilla-like > browsers) or the innerText (IE-like browsers) of the element, which is > the rendered text shown to the user. > > So I'm guessing that since we can manipulate "innerText" with > IE/Watir, I'll be we can manipulate "textContent" with fireWatir. > > So it might make sense to abstract both commands into a > "munge_text_directly" method. > The Watir::IE method for storeText is "text". This amounts to a convenience method that wraps innertText.
Watir does not currently directly support changing page content, although you can can do this, as this thread has discussed, using the ole_objects. Neither Watir nor Selenium nor FireWatir currently provides commands for munging text directly. To me this sounds like something that is outside the scope of a testing tool. Can you elaborate on the scenario that makes you want to do this? Is it testing related? Bret _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
