fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
fu ([personal profile] fu) wrote in [site community profile] dw_beta2012-03-24 01:20 pm

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:

  • 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!
unicorn: a unicorn skull. (Default)

[personal profile] unicorn 2012-03-24 06:59 am (UTC)(link)
The extra rows combined with the fullsize icons in the new icon selector gives me visual fatigue; I went into it a little more here. I would love it if we could at least have size options on the selector like we did in the previous one.
memorable: (pic#1509741)

[personal profile] memorable 2012-03-24 07:02 am (UTC)(link)
I'm also having problems with this! The number of icons in a row plus the size of the icons is way too much for me to handle.
all_that_glitters: (gilgamesh094)

[personal profile] all_that_glitters 2012-03-24 07:11 am (UTC)(link)
Yes this! I'd like it more with less columns and options for sizes.
antreegonist: Mithos: symbolic/World Tree sapling (a dream deferred.)

[personal profile] antreegonist 2012-03-24 07:16 am (UTC)(link)
Yeees, this, especially with over 200 icons to sort through.
unwieldyfate: what (Then who was Archer?)

now commenting in the right place!

[personal profile] unwieldyfate 2012-03-24 07:27 am (UTC)(link)
Hi! I wanted to second the visual fatigue issue with the new icon browser. It gets especially bad in premium accounts with over 150 icons, I think. Though in my case I believe it's more a matter of the width+showing so many icons per row—I find it more difficult to scan icons that way.

It may very well be a case of getting used to change, but I wanted to add my .02 anyway.
basilmemories: (Scholarly pursuits.)

[personal profile] basilmemories 2012-03-24 07:40 am (UTC)(link)
Same here! I brought it up here, but just to ass the technical parts:

My main browser on the pc is firefox 10.2, I'm using the most recent android browser, and the laptop was chugging along on firefox 6 or 7 or so, it needs updating.

I'd like to see some size or column options for this, I understand that you don't intend to alter the size options? but I can't run greasemonkey on my phone (which I'm on more and more these days), at least not without using android's firefox, which is a steaming hot mess and a memory hog on my device.
basilmemories: (Failgun is Fail)

[personal profile] basilmemories 2012-03-24 07:44 am (UTC)(link)
*assess I. Thank you for that typinghands, stay classy.
nevergetscredit: (Neutral: Watching over things)

[personal profile] nevergetscredit 2012-03-24 08:38 am (UTC)(link)
I am having the same issue. But the fullsize icons in the previous browser never gave me that problem, so I'm not exactly sure what's causing it for me this time. Possibly it might be the white colour of the browser? Somehow when it's on top of the greyed out page it looks kind of bright and glaring.
zaluzianskya: (Default)

[personal profile] zaluzianskya 2012-03-25 01:49 am (UTC)(link)
Size options would be great. Since some people have issues with the fullsize images and others (myself included) hated the smaller images, what about making it just default to whatever you chose last? That was my main issue with the old browser, that it would always default to smaller images even though I preferred the fullsize ones.
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2012-03-25 02:12 am (UTC)(link)
Agreed on the old size behaviour! Though I definitely like having more than two columns in the new browser, too :)