[EMAIL PROTECTED] wrote on 19/08/2005 01:20:40 AM:
> On Thu, Aug 18, 2005, Alexander Dvoretskiy wrote:
> >
> >
> > I suggest
> > 1. Remove all the implicit trimming and removeNbsp calls,
> > 2. Add special assertions like assertTrimedText.
> >
>
> Objection! ;-)
>
> HTML output trims spaces -- I've run into a few bugs because of this.
> I'd much rather the default do the trimming just like HTML display. You
> should create assertUntrimmedText. (The other reason, of course, is
> that changing semantics is usually a Bad Idea and requires considerable
> justification -- I don't think you've met that standard yet.)
>
This looks like something that could be supported via the suggested syntax for specifying transformations like converting to lower case (to allow for case-insensitive matching).
If we were not already trimming then the syntax might be something like:
assertValue | foo | trim:tolower:regexp:^fo*$
We have not actually reached release 1.0 and so I think users must realize that the interface may change. However, given that lots of people seem to be making serious use of Selenium, we could leave the default behaviour as is, but support both "trim" and "untrimmed" for those wanting to be explicit about it.
e.g.
assertValue | foo | untrimmed:tolower:regexp:^fo*$
Cheers,
David
David Kemp
ThoughtWorks Australia Pty Ltd
http://www.thoughtworks.com
_______________________________________________ Selenium-devel mailing list Selenium-devel@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
