-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Picker组件多列模式下传入data时,如果name的值的长度过长出现截断符号后,两个列会错位 #1311
Comments
并且右侧列会无法滑动 |
1uokun
added a commit
that referenced
this issue
Sep 19, 2023
如何复现"两个列会错位" @DreamEVA |
const data = [
{
label:'00000000超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label',
value:'1',
children:[
{
label:'0000超长的labell',
value:'1-1',
},
{
label:'超长的label',
value:'1-2',
}
]
},
{
label:'00000000超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label超长的label',
value:'2',
children:[
{
label:'超长的label超长',
value:'2-1',
},
{
label:'超长的lab',
value:'2-2',
}
]
}
];
// 在小屏幕的设备上能稳定复现<List>
<Picker
data={data]}
value={state.CKCode}
cols={2}
onChange={(value)=>{
setState({ CKCode:value });
}}
itemStyle={{
paddingTop:8,
paddingBottom:8,
}}
>
<List.Item arrow={'horizontal'}>仓库仓区-库位</List.Item>
</Picker>
ぃ不幸少年℡
***@***.***
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2023年9月19日(星期二) 晚上6:03
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [ant-design/ant-design-mobile-rn] [Bug] Picker组件多列模式下传入data时,如果name的值的长度过长出现截断符号后,两个列会错位 (Issue #1311)
如何复现"两个列会错位" @DreamEVA
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Merged
Merged
fixed in 5.1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
💬 前提强调
🙋 描述详情/重现步骤
Picker组件多列模式下传入data时,如果name的值的长度过长出现截断符号后,两个列会错位
💻 运行环境
Android
⚫️
npx react-native info
输出信息补充说明
No response
The text was updated successfully, but these errors were encountered: