Opcode table layout/render issues

[dorlevi]

The Opcode table layout seems buggy on my browser with a massive gap between the input and output columns and issues with horizontal scroll

[dorlevi]

[peroket]

It's not broken, it's because at the end some inputs are big, but yes I would also prefer the width of input smaller

[dorlevi]

Yeah, but it should "stack vertically" or another solution, for example, if it's multiple inputs and it's too long we can truncate and let people expand "input1, input2, and 3 more *expand*" it's not ideal to sacrifice legibility for these few opcodes with long inputs.

…

On Mon, Oct 25, 2021 at 8:12 AM Adrien Hamelin ***@***.***> wrote: It's not broken, it's because at the end some inputs are big, but yes I would also prefer the width of input smaller — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALD6HX5TZL3VPEDDFX6WMLUIVCSDANCNFSM5GVDSCHQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[assimovt]

Yep, aware of the table fitting issue. Partially, will be addressed in #22 (by hiding some columns) but the input/output is an issue indeed. I was thinking about expanding by clicking ... in the [x]...[z], but then it will push the column wide anyways - not really a nice solution. Breaking it into multiple rows might look weird as rectangles won't look nice and will push the row to be too high. How about we show only the first 3, then ..., then hover would show the tooltip with full input stack?