We currently (read: with most recent webdsl version) have weird ajax replace behaviour on the researchr website.

It had no problems running an older webdsl version, but with the head trunk webdsl version it has problems repainting an expanded facet cloud.

Steps to reproduce:

• Open dutieq’s test researchr: click
• Click Tag to open the tag cloud (works fine)
• Now click the [+] to expand the number of Tag facets. In firefox/chrome/? it fails to repaint the facet cloud
• Now, when you click any tag facet (in the outdated cloud), it will repaint the facet cloud and the tag you clicked is one from the expanded facet cloud.

Submitted by Elmer van Chastelet on 17 September 2012 at 12:39

Tested with older webdsl r5303 -> Still the same problem. Now going to test older researchr revision.

Researchr r740/ webdsl r5350 -> Failed to repaint correctly

Trying webdsl r5273

Researchr r740/ webdsl r5273 -> works fine

Researchr r747/ webdsl r5273 -> works fine

Researchr r747/ webdsl r5275 -> Fails to repaint correctly

So it is related to this relatively big change, see websvn webdsl r5275

Might be due to lucene jar updates, bobo-browse jar updates, or code that handles the retrieval of facets.

Fixed in WebDSL r5360

And, what was the problem?

The administration of facets in WebDSL (AbstractEntitySearcher.java) didn’t change the maxCount facet parameter on change. (introduced with ‘facet selection’-aware facet retrieval, webdsl r5275)

However, I still don’t understand why it caused the ‘repaint’ kinda problem, or more detailed: why clicking the out-dated facet value caused filtering a different value than clicked.