This is a test to check for things like we saw in bug 4949.
The issue was that a connector springeropen.cf worked fine in
local tests, but failed on the (production) engine. Turns out
that things depended on the version of Firefox where the builder
was running, and the version of the xulrunner under the cf-zserver.
The crucial difference was that the page,
http://www.springeropen.com/search/results?terms=water
contained nested P tags. Or, to be precise, a
P tag that contained
STRONG tag that contained
A tag that contained
P tag that contained the actual title.
Nested P tags are not allowed in strict HTML. Firefox 3.X didn't mind,
and build a DOM tree that reflected the source. Firefox 8.X did mind,
and built a quite different DOM tree, closing all open tags when it saw
the second P tag, reopening everything, and then closing the tags again.
In the end it saw the closing P tag, and opened a new P so it could close
it. The result was two P tags in sequence, both containing a STRONG and A,
but only the second had the title.
Since the original connector was built with FF 8.x, it had an XPattern with
many empty P tags, and it worked fine locally. But on the production engine,
which was running on xulrunner 1.9, the DOM tree was different, and the
XPattern failed.
So here is a test case:
Some text about the second hit
The pattern that matches this example, under firefox 8, is
p { strong { a $title [ @href $url ] } } : strong : p : span $description
Note the two STRONG tags, although there is only one in the HTML.