a #UX question. If a site has both a signed out home page, and a signed in one (for example a feed or dashboard), what should you see if you're signed in and try to view the home page?
for example, if I go to figma.com or twitter.com I see my signed in home page. If I go to mural.co I see the signed out one, and have to manually click to the signed in one
@benjamineskola I'm leaning to the same, but it does feel odd that theres a page you can't see when you're signed in. But then it also feels odd to me that I can't just type mural.co and see my dashboard
@benjamineskola I think you hit the nail on the head with access to the same information. So for example you should be able to find out about pricing and whatever even if you're signed in
@eviljonny yeh it annoys me too, I think I'll avoid it on my project. @benjamineskola put it well - the same info should be available to you either way
The loading attribute on an <img> element, or the loading attribute on an <iframe>, can be used to instruct the browser to defer loading of images/iframes that are off-screen until the user scrolls near them
Got a Playwright question - in my tests I'm clicking a button which in the backend sends an email. I tried to use Jest to mock that function in the backend so it doesn't send an email, but that doesn't seem to work. Should it?
I could check for NODE_ENV in the backend and not send an email, but I'd like access to the email contents in my playwright test, but without actually sending an email.
Am I right in believing everyone has access to #GitHub#Codespaces for public projects these days?
I wanted to be able to use them for some training stuff
@samb You're sorrier than I am! But I am sorry as well. I am as sorry as you are, Dimitri. Don't say that you are more sorry than I am, because I am capable of being just as sorry as you are.