LW Update 2018-08-23 – Performance Improvements

post by Raemon · 2018-08-24T02:02:30.916Z · score: 20 (7 votes) · LW · GW · 6 comments

Today's deploy includes:

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.


Comments sorted by top scores.

comment by tcheasdfjkl · 2018-08-24T02:24:10.000Z · score: 7 (4 votes) · LW(p) · GW(p)

bug report: hovering over a comment's score displays "voteCount Vote"

comment by Raemon · 2018-08-25T01:22:20.123Z · score: 2 (1 votes) · LW(p) · GW(p)

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.

comment by Michaël Trazzi (mtrazzi) · 2018-08-24T20:36:00.353Z · score: 1 (1 votes) · LW(p) · GW(p)

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".

comment by Vladimir_Nesov · 2018-08-24T03:23:14.149Z · score: 0 (2 votes) · LW(p) · GW(p)

Bug: Since a couple of weeks ago, I no longer receive notifications for replies to my comments.

comment by Raemon · 2018-08-24T20:50:16.531Z · score: 6 (3 votes) · LW(p) · GW(p)

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.

comment by Vladimir_Nesov · 2018-08-25T03:47:19.776Z · score: 2 (1 votes) · LW(p) · GW(p)

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.