LW Update 2018-08-23 – Performance Improvements
Today’s deploy includes:
Removed the map of meetups from frontpage since the major Slatestar Everywhere push is wrapping up.
Posts with lots of comments should load faster now
Fixed the bug where the last post in a sequence wouldn’t properly navigate to the next post in some cases.
Printing a page now should work more nicely without stylesheet glitches.
Continued refactoring our style management in preparation for EA Forum and AI Alignment Forum theming. In the process, we:
streamlined some of our font sizes
updated our Form styling
made most UI elements sans-serif
In some cases the styling refactor has caused some edge cases and less common sections of the site to not quite render properly, which we apologize for and are continuing to work on.
bug report: hovering over a comment’s score displays “voteCount Vote”
Mini update: I fixed a few cosmetic stylings.
A major issue we’re looking into right now is the datetime component. The older version of Material UI we used to use had a datetime component that left something to be desired – you had to click through a clunky UI to set the time (and couldn’t easily edit the text. So if you wanted to change an event from 7:00pm to 7:30pm you had to navigate through some buttons and click an up arrow a bunch of times)
We’ve migrated to Material UI 1.x, which no longer bothers pretending to have a good datetime component and instead relies on the browser’s… but it turns out Firefox doesn’t actually have a datetime component at all, and Chrome’s isn’t that great.
Apologies to people trying to set dates in the meanwhile.
Bug: On Chrome using a Samsung Galaxy S7/Android 8.0.0 the “click and hold” thing does not work. Same with the “click to see how many people voted”.
Bug: Since a couple of weeks ago, I no longer receive notifications for replies to my comments.
Hmm. I’m not sure why this would have changed, but I note that in your account settings the “notifications for replies to comments” is unchecked.
So sorry about that. I did try to switch to Markdown at that time (Markdown was unresponsive, so I switched back), possibly visiting the settings form for the first time, and there’s NoScript running in my browser. But more likely just clicked there by mistake, even though I can’t imagine how that could happen.