Mar. 24th, 2012

fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[personal profile] fu
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!
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[personal profile] fu
I'm looking for someone willing to comb through the comments for the [site community profile] dw_beta posts on the new create entries page and put them into zilla for me <3

I'd do it myself, but I keep getting bogged down in trying to *fix* the bugs instead of filing them, and that means that most of the later reports keep getting put off.

Needs: patience, data processing skills, the ability and patience to interact with Bugzilla.

What to do:
Go through the entries tagged "create entries", and look in the comments for everything that should be filed. File a separate bug for each issue encountered, that hasn't been fixed yet.

I've commented to a lot of threads when there's something that's I've fixed, but there are some where I haven't. If you're not sure whether it's been fixed or not, I'd suggest you go ahead and file it! If it looks familiar, we can mark it as DUPLICATE. It's easier to mark something as duplicate, than to go hunting through all the comments again for anything that we might have missed.

If it's a duplicate of an existing, but not fixed, bug, that's also fine, we can also mark it as a DUPLICATE, easy enough.

If it's a feature request rather than a bug, and it's not something that's already been shot down: file it anyway, we can choose to either do it, or WONTFIX it, but either way we'll handle it.

The important thing is to get things organized in a form where we can quickly accept or reject them, and quickly pick them up to fix.

Comment here if you're interested!
Page generated Oct. 18th, 2017 11:23 am
Powered by Dreamwidth Studios