You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This also happens on v0.8.0. @skv-headless, i know you don't want to add tabBarStyle prop but with this issue it won't be possible to remove the bottom border.
same issue here on v0.8.0. @skv-headless.
I manually replace this.props.scrollValue._value to this.props.scrollValue.__getValue() and resolve this issue.
@skv-headless we are expecting you have plan checkin the fix into v0.8.next release, to avoid we re-package or find not ideal workaround from caller side.
Activity
zhangxiaoyu1314 commentedon Jun 23, 2017
+1
GreyLove commentedon Jun 27, 2017
+1
cricketnest commentedon Jul 1, 2017
the same issue, but for default scrollableTabView.
Clcll commentedon Jul 6, 2017
the same. .. did you solve this issue ?
iambatoan commentedon Jul 10, 2017
does someone have any solution? same issue for
thaiminh commentedon Jul 10, 2017
same issue here :(
nishiltamboli commentedon Jul 10, 2017
Downgraded to 0.6.6 and the first tab opens up fine. The underline seems to work correctly. Something went wrong with 0.6.7.
CodingMonkeyzh commentedon Jul 10, 2017
replace
this.props.scrollValue._value
tothis.props.scrollValue.__getValue()
can resolve this issue.oureta commentedon Dec 15, 2017
This also happens on v0.8.0. @skv-headless, i know you don't want to add
tabBarStyle
prop but with this issue it won't be possible to remove the bottom border.wanghz2 commentedon Jan 4, 2018
possible fix in caller side? overwrite the imported function?
arfaWong commentedon Feb 9, 2018
same issue here on v0.8.0. @skv-headless.
I manually replace
this.props.scrollValue._value
tothis.props.scrollValue.__getValue()
and resolve this issue.gmaggio commentedon Apr 2, 2018
The suggested
this.props.scrollValue.__getValue()
seems to fix the problem. Just wondering but why isn't it implemented yet?wanghz2 commentedon Apr 20, 2018
@skv-headless we are expecting you have plan checkin the fix into v0.8.next release, to avoid we re-package or find not ideal workaround from caller side.
2 remaining items