@Luke I can suggest looking into Panic’s Nova and Polypane. The first has a browser tab inside the editor with live reloading, the other is a browser customized for developers. Neither has quite what you’re after but may be useful?
@simevidas@hi_mayank Not specific to custom elements, seems to happen to any empty inline element. The element itself has non-zero height, its parent div has zero height, chaos ensues. Probably related to one of these?
Yup, for node dev at least “node –test” and “node:assert” is absolutely good enough. (Mocha via web-test-runner is still IMO the best option for front-end unit testing, tho.) https://evertpot.com/bigint-money-2/
@baldur Pretty happy with it! Wish it had a nicer reporter built in (eg. I had to comment out Skipped tests because they were getting on my nerves), but solid foundation.
Today’s thankless task: figuring out what about my bog-standard, non-JS, bag-of-HTML-pages of a personal website compels iOS Safari to jump to the top of the article every time I hit the back button, instead of maintaining the scroll position, when visiting any external link.
Alright, that was quick. The tabindex=-1 on <main id='main'> causes iOS Safari to activate the element and scroll it into view when returning to the page. I will look for (and file) a bug for that.
But… @aardrian also has <main tabindex=-1> on his blog, to no ill effect on iOS Safari…
@siblingpastry@aardrian It resets the scroll position to the top of <main> when returning to the page after navigating away from it. I'll try to clarify the title / content.
@siblingpastry@aardrian Well, in addition to focusing on <main>, iOS Safari scrolls to the top of it. It loses my place on the web page when I follow links.
@siblingpastry@aardrian I merely mentioned document.activeElement = main as what tipped me to finding the root cause. It's the scrolling to top that’s problematic.
Why can't I get my dates to display in the right timezone? Why is this impossible? Why does it have to be different in production? Why does it have to be so hard?
I thought I had a fix using date-fns-tz, but I still can't get it right on the server.
@mia@Meyerweb It sounds like you‘d want to reassign (not convert) the datetime from the Denver timezone to UTC, to keep up with the expectation? Does not have a direct incantation in date-fns-tz.