Closed GZGavinZhao closed 2 years ago
Fixed by 73bea40aaf88656f563fa6a7eba07e5488cfd5f8. Through my testing, _currentZIndex
is never null as long as ZIndexer
has been used (through the Angular DI). The solution is to add another variable to check whether ZIndexer
is used and set _currentZIndex
accordingly.
This only applies to the v2.0.0-dev.X series alpha release (I.e. the
dev
andnew-dev
branches). Please try using these branches in your projects and tell us whether this is indeed an issue!In my opinion, the current null safety implementation of
ZIndexer
has a caveat:In the function
_initZIndex()
,_currentZIndex
can never be null. However, according to testing with the non-null-safety version (the default template project created byngdart
is enough; after entering an item, hover above the checkbox), when the first timeZIndexer
is used,_currentZIndex
is definitely null. Therefore,_currentZIndex
is never set tohoverableAutoIncrement
and just seems to be... a random number? However, I don't see any errors or weird behaviors when I test the current implementation.Just putting this problem out here for now. I will do some further investigation tomorrow.
Affected components:
material-popup
, which in turn means:material-dropdown-select
material-tooltip