Blueprint: ItemPredicate make onActiveItemChange fired twice and active item isn't the good one

Created on 25 Jun 2020  路  3Comments  路  Source: palantir/blueprint

Environment

  • __Package version(s)__: 3.28.1
  • __Operating System__: Mac OS - latest
  • __Browser name and version__: chrome Version 83.0.4103.106 (Build officiel) (64 bits)

Steps to reproduce

  1. Define a Select component with a custom item list render and item render
  2. Add itemPredicate function
  3. select an item
  4. Open the Select back ( active item isn't item selected )

Actual behavior

I don't know why but onActiveItemChange is fired twice when a itemPredicate is defined. First you get the selected item and just after onActiveItemChange is fired with the first item in the list with no reason.

Expected behavior

ActiveItem is the selected item when you open the list after a select.

P2 select bug help wanted

Most helpful comment

Any update on this issue? I can reproduce it as well.

All 3 comments

See in live in this code sandbox : https://codesandbox.io/s/strange-lamport-3zowo?file=/src/App.js

Notice that when you add the predicate the selected item isn't active when you re-open the select.

I also let some meaningful console.log that show you why this bug occurs.

Can confirm the repro:

2020-06-29 11 57 24

Any update on this issue? I can reproduce it as well.

Was this page helpful?
0 / 5 - 0 ratings