![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
New JS on Journals: Last Call
We're planning on taking the "new JavaScript on journals" changes out of beta soon and making the changes the default for the entire site, so we've done a push today that adds the last few (reported) missing features, and fixes the last few (reported) really annoying behaviors.
There's always going to be one thing more though, so please make sure that you turn on beta for the new JS on journals, and tell us how that new JS works for you -- or doesn't work, if that's the case.
I'm interested in hearing about everything that's bothering you, no matter how tiny it seems! The sooner we know, the sooner we can fix it. (Just this code push, we fixed two things that seemed tiny: one was the hover menu fading way too quickly, another was how the attempt to change your poll vote would bring to you to a separate page instead of changing your vote on the page you were on. They were both things we missed at first, but once they were brought to our attention, we couldn't stop seeing them. And now they're fixed!)
So poke around, and let us know what you find. If you're looking for something to focus on, here's a short list of things we recently added or fixed:
Assuming there are no major issues, we'll turn on the "new JS on journals" beta flag for everyone with our next code push for one last round of testing with the whole site, not just the people who've turned on the beta version. We'll keep it as a beta option at that point, so if anyone has serious problems, they can disable the beta and go back to the old JS while we fix the problem. After that, we'll take this code out of beta and make it the standard option for everyone, removing the old (existing) JavaScript entirely. So, if something's wrong, speak up now!
There's always going to be one thing more though, so please make sure that you turn on beta for the new JS on journals, and tell us how that new JS works for you -- or doesn't work, if that's the case.
I'm interested in hearing about everything that's bothering you, no matter how tiny it seems! The sooner we know, the sooner we can fix it. (Just this code push, we fixed two things that seemed tiny: one was the hover menu fading way too quickly, another was how the attempt to change your poll vote would bring to you to a separate page instead of changing your vote on the page you were on. They were both things we missed at first, but once they were brought to our attention, we couldn't stop seeing them. And now they're fixed!)
So poke around, and let us know what you find. If you're looking for something to focus on, here's a short list of things we recently added or fixed:
- added same-page comment tracking
- fixed same-page changing of poll votes
- added displaying errors when comment expansion fails to work
- fixed hover menu fading away even when you didn't move your mouse
- fixed the .cuttag-open CSS class so it applies to the contents of the opened cut tag (the way the old JS did), for people who want to customize this in their styles
- made the bottom arrow jump you to the top of the cut tag, without affecting page forward/back
Assuming there are no major issues, we'll turn on the "new JS on journals" beta flag for everyone with our next code push for one last round of testing with the whole site, not just the people who've turned on the beta version. We'll keep it as a beta option at that point, so if anyone has serious problems, they can disable the beta and go back to the old JS while we fix the problem. After that, we'll take this code out of beta and make it the standard option for everyone, removing the old (existing) JavaScript entirely. So, if something's wrong, speak up now!
no subject
The interface isn't the prettiest, but it's clean and minimalistic, which is a breath of fresh air, as other sites do not have this, or are changing from it. Why they would do this, I don't know.
The interface that you have for browsing tags is lovely too, but maybe you could somehow work it so longer tags are still on one line?
I am not sure how LiveJournal does it, but their tag browsing interface has that. If I recall correctly, the longer ones kind of fade before they get to the next column (so you don't see the whole thing), instead of wrapping to the next line like yours does. I think that LJ's version might not be good for longer tags that need to be read completely.
Maybe you could do a smaller font? I have terrible eyesight, and I am sure that something a bit smaller wouldn't hinder me, maybe something along the 9-10px range.
One more added critique for the tag browser, is that instead of having the list go from left to right like this:
A B C D
E F G H
It could go like a typical list:
A E
B F
C G
D H
I just think that might be a little easier, as the eyes naturally go down and then up and over when reading lists, while with full paragraphs with text, they go from left to right and then down to the left again.
But all in all, this is a wonderful posting page and I love it!
EDIT:
Also, still on the topic of the tag selector, could it be possible to have the "save" button down at the bottom of that screen? It's kind of awkward for it to be up in the top right when all other save or update buttons are down at the bottom left or bottom right.
But this is just minor and me nitpicking, I am sure that there are lots more important suggestions.