oh, I actually played with the Amazon site before replying to you and the quick (too brief) experiments I had done seemed to endorse my theory.
After a better look now, it seems they apply a different strategy depending on the selection; I think the way they do it makes sense but it's impressive that the user is fooled into a non-consistent API, and it still "feels" like all is consistent. On 3 June 2013 14:10, Emmanuel Bernard <emman...@hibernate.org> wrote: > On Mon 2013-06-03 10:28, Sanne Grinovero wrote: >> On 3 June 2013 09:59, Hardy Ferentschik <ha...@hibernate.org> wrote: >> > >> > On 31 Jan 2013, at 11:32 PM, Emmanuel Bernard <emman...@hibernate.org> >> > wrote: >> > >> >> I know we had a debate but I can't seem to find any detail in the >> >> documentation about how facet selection influences the facet counts. >> >> >> >> In my demo, the facet count is applied after the selection. ie if I do a >> >> query that returns '< $100' = 20 and '> $100' = 45, once I select '< >> >> $100', the count displayed on '> $100' = 0 which is very weird from a >> >> use point of view. >> >> Right that looks weird, but shouldn't you be hiding the other facets >> after having selected one? >> I would expect a UI to potentially show new sub-facets only, to allow >> a user to drill into more details. > > The thing is, if you select a price range, you want to be able to select > the other price range, so you can't "hide it". > > Play a bit with Amazon's version > http://www.amazon.com/s/ref=sr_nr_p_n_size_browse-bin_3?rh=n%3A3151491%2Ck%3AUSB%2Cp_n_size_browse-bin%3A1259713011&keywords=USB&ie=UTF8&qid=1370264935&rnid=1259751011 _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
