New changes live

[fu]

New with this code push, including fixes so that the JS always works even when expanding multiple layers, e.g., even after viewing answers, or after expanding a cut:

• polls


• media placeholders


• contextual hover


• expand all cut tags module

And a couple of tweaks, chiefly:

• fix quick reply overlapping content in some layouts


• make screened/delete/etc work for expanded comments

Comments

[erika]

You are bright & shiny!

[samjohnsson]

hi, bug. When I'm on my reading page, I see the pulldown arrow next to cut tags properly (well, most of them - it gets inconsistent past the first page). When I'm on my Recent Entries, no arrows at all. Dunno if this is a theme thing, or a .js thing. It's been going on for a few days, though.

[melannen]

As of today, I no longer get pulldown arrows on any cuts at all.

Edit: Scratch that, I get them on my Recent Entries page but not my Reading page.

[fu]

Belatedly, I think I know what's causing it (userhead in the subject line + contextual hover + beta is breaking all JS on the page), and hope to have it fixed by next push.

[yvi]

Oh, wonderful. I was confused why sometimes cut tags worked and sometimes they didn't.

[fu]

Cut tags should work all the time now -- if ever they don't, just holler!

[mklutz]

The only issue I've noticed since turning it on is that when I try to unsubscribe from tracking a thread I don't get the context hover, but am instead taken to the edit subscription post. Once there, even though I've unchecked the relevant boxes, I am still subscribed somehow.

[mklutz]

In case you need it, here's an example of a thread I've removed my subscription to, but it still shows me as subscribed.

[fu]

Just had a chance to look into this -- threads removed using the checkbox on the page are deactivated and can be permanently deleted using http://www.dreamwidth.org/manage/settings/?cat=notifications. There should be a grayed out line in there (or use the "Delete all inactive tracked items" button)

We don't have the on-page context hover yet, but we'll work on including that into beta soon. (It's one of the last big features left on that page). Thanks for the report!

[yvi]

I just got this error:

Permission denied for <http://embedded.dreamwidth.net> to call method Location.toString on <http://yvi.dreamwidth.org>.

Not sure if it has anything to do with beta.

[fu]

Nope! It has to do with some JS in iframes that's (as far as I can tell) trying to look up its URL. It doesn't seem to cause any issues, other than cluttering up the logs some.

[sarken]

Hi, there! The Dreamwidth Beta page says same-page poll submission should be working with the new JS beta, but it isn't working for me. I'm using Safari 5.0.6 on Mac OSX 10.5.8, I have the beta update page turned on as well as the new JS beta, and I'm using the Transmogrified layout with custom CSS, but it works when I turn the new JS beta testing off.

[amadi]

I second this, using Firefox 8.0.1 on Mac OSX 10.6.8, though I tested across a half dozen different accounts and only the account that has JS beta and the update page beta testing turned on had the problem, on any layout, custom CSS or otherwise.

Clicking submit on a poll, whether from the basic journal page or from the reading page, automatically forwards to the specific entry that the poll is attached to.

[fu]

Hmmm. Okay something weird is definitely going on. After you try to respond to a poll and it redirects you, can you open up Tools > Web Developer > Error Console; look in the Errors tab and tell me if there's anything there?

(Using FF 8, on Mac OSX 10.6.8, I'm not running into any problems so there must be another trigger for it!)

[amadi]

I took this poll from my reading page, and it did drop me into the entry itself when I clicked submit. There's a bunch of errors in the error log, can I email you a screenshot of it?

[fu]

Yes please! My dreamwidth.org address works fine :)

[amadi]

Just sent. Thank you!

[fu]

Hmm, very odd. It's working for me in Safari 5.1.1, also on Mac OSX 10.5.8; there shouldn't be that big a difference though.

Trying to think of other factors that could contribute
* are you viewing the poll on your reading page, or are you viewing it on the journal entry itself?
* I'm guessing it happens with all polls, rather than just a specific poll or group of polls?
* could you open up the error console please -- Develop > Error Console, and let me know if there's anything showing up on that front after you post the poll?

[sarken]

This is pretty odd. I've had it happen at least three times recently -- once from my network, twice from my reading page -- but when I posted a poll to my own journal, it worked fine from the entry page. I went back to me reading list, cleared the answers from a poll I'd had the issue with, filled it out again...and it worked fine. It seems to be an off and on thing for me, with all types of polls. Since it worked fine just now, I didn't see an errors on the error console. If it happens again, I'll check the error console and report back.

[fu]

By any chance, do you have any extensions or scripts that run on DW? (I know that Safari has the ability to adapt GM scripts to use in the browser).

And if you do, can you try testing with them on and off (if you can find a poll where it's breaking)?

[sarken]

No, I don't have any extensions or scripts I use for Dreamwidth -- but I also haven't seen the problem again, so yay?

[fu]

Hmm I can think of either one of two things: we've made a few tweaks to JS code, and we've fixed a few performance issues that might have caused the poll results to load too slowly back then.

Either way, I'm glad for that! But let me know if you run into any issues again :)

[anxiouswiz]

same problem with my web https://anxiouswiz.com/