Content
@
0 reply
0 recast
0 reaction
@undefined
new farcaster frame spec proposal "fc:frame:input:button" "fc:frame:input:button:(icon | text)" what - adds a button with desired icon or text for input current problems - 4 buttons are too limited already but also have to be used for validation, navigation, etc. solution 👆🏻 @horsefacts.eth @dwr.eth @v
21 replies
9 recasts
32 reactions
@undefined
with the update, i would be able to remove the navigation buttons from my frame. this issue is not just for me, but all frame devs observe @nikolaiii's frame for example - buttons have to be multi functional depending on input which is both confusing for users and devs https://altumbase.com/ham/8152/Ib8SDSvR6x
1 reply
0 recast
1 reaction
@undefined
i feel like having a designated input for input text could be super powerful imo can be used for - navigation - input validation - input dependent functions thoughts frame builders? @nonlinear.eth @dalechyn.eth @nikolaiii @downshift.eth @edit @matthewfox @codincowboy @apex777.eth
2 replies
0 recast
3 reactions
@undefined
for example @nikolaiii 's search input could have a search icon at the end https://warpcast.com/undefined/0x1b324011
1 reply
0 recast
1 reaction
horsefacts
@horsefacts.eth
Nav buttons are a pretty common pattern, maybe they should get their own chrome too.
1 reply
0 recast
2 reactions
@undefined
could you elaborate what you mean by "own chrome"? i think using 2/4 buttons for navigation hurts the end user imo - especially for complex frames like moneygun with more than 3 pages to deliver
1 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
Dedicated buttons, like you might see on a carousel component.
1 reply
0 recast
0 reaction
