ytry0121• 250
@ytry0121
Submitted
Any comments are highly welcome!
antoine
@antoineterny
All comments
- antoine• 345
@antoineterny
Posted
Hello ytry0121, great work ! It would be nicer though without the scrollbars. I think you can avoid the overflow by collapsing all the other dropdown when you click on one of them. And also it would be nice if the cursor was a pointer when you click on a title to close it. Cheers
0 - antoine• 345
@antoineterny
Submitted
This one was difficult! I never had made use of 3D css before, that was interesting. But I ran into strange display bugs in the browser, probably due so some sort of difficult to debug race conditions. Eventually I managed to hide them as much as possible but I think my logic is far from perfect. Tell me what you think!
antoine• 345@antoineterny
Posted
Hello ApplePieGiraffe, thanks for the hint ! I hadn't noticed yet this very useful accessibility report, everything is in order now, thanks to you 🙏
1 - antoine• 345
@antoineterny
Submitted
Hi everybody ! This was my first use of React hooks, and I thinks the code is leaner that way. I couldn't find a way of displaying the tablets accordingly to the design without using flex gap, and couldn't find a fallback for navigators which don't support it yet. What do you think about it ?
antoine• 345@antoineterny
Posted
Hi VoyageinStyle, I stored each criterion in an array like ["language", "javascript"] So here crit[0] is "language" and crit[1] is "javascript" We want to filter the complete list of jobs in which job["language"] is equal to "javascript" You have to be aware that you can find a property in an object with the key as variable between square brackets. Here, job[crit[0]] is equivalent to job.language Hope it helps ! Cheers
0 - antoine• 345
@antoineterny
Submitted
Hi everybody ! This was my first use of React hooks, and I thinks the code is leaner that way. I couldn't find a way of displaying the tablets accordingly to the design without using flex gap, and couldn't find a fallback for navigators which don't support it yet. What do you think about it ?
antoine• 345@antoineterny
Posted
Hi emestabilo, thanks a lot for your feedback! I hadn't noticed this bug, indeed it was not the expected behavior I guess, it is now fixed thanks to you. Oops ! And thank you for these interesting resources but they don't solve the problem since it only occurs when the tablets go "flex-wrapping", and CSS is not aware of who's wrapped and who's not! Hence this super cool gap property which I hope will be supported by every browser very soon (https://www.caniuse.com/?search=flexbox%20gap) Cheers, Antoine
0
