JS Conversion Beta: Report issues here!

[denise]

If you're participating in the JQuery conversion beta test, report any issues you find here!

Currently, here are the things that have been implemented (and not implemented):

Implemented

Cut expand and collapse
Logging in
Screen/freeze/delete
Control strip injection for non-supporting journals
Quick reply
Thread expander

Not implemented

Contextual hover
Media embed placeholder expansion
Same-page poll submission
Icon browser
Same-page comment tracking


(This means that if you try to do something on the "not implemented" list while you have the beta features turned on, you'll be routed to the non-Javascript/non-inline version. That isn't a bug and you don't have to report it, but you should report anything else that's weird or that doesn't behave the way it used to!)

Comments

[florahart]

Okay, so I turned on the beta thing because I use multiple browsers in different settings so am likely to notice things what don't look alike?

And then I attempted to leave the news post after clicking on a reply to a comment (the thing I just replied to, about the suggestion to make the icon show in the preview). Once I had opened the comment box, I was not able to go anywhere on DW without commenting in it. As this has never happened before, and I surely would have noticed, so I surmise it's either this or something else about the recent code push.

Okay, I mean, I didn't test every possible thing. I didn't click away to a different tab and come back, which I will test here in a sec. But once that comment box was open, I could not go to my reading page, or my profile, or anywhere else; every attempt brought me back to the box.

Bzuh?

On this machine: Linux (Kubuntu), Chromium 7.0.528.0

[florahart]

Clicking away: no help (didn't think it would be). I can, however, change WHERE I am commenting; I can reply here, or I can click the post new comment link. Nothing else will go anywhere but here.

[fu]

How embarrassing -- I've found what was causing the issue, we'll have that fixed by next push.

Thank you, awesome catch!

[fulminata]

I'm trying to reply to a comment and enter in a subject. When I click in the Subject field, the cursor automatically tabs into the Message box. I refreshed the page and the same issue occurred.

Using: Firefox 4.0.1 / Windows 7 Starter (if that's needed)

[fu]

Should be okay now, thanks for the info!

PS. Love the icon.

[ciaan]

I'm also having problems commenting, and it's not happening on LJ, only here. Windows XP Professional, Firefox 3.6.16. When I'm typing in the comment box I can't click into the subject line OR click back to another part of the comment. So if I make a typo, I have to erase back to there using the backspace key to fix it, can't just click there with mouse or use arrow keys. Also when I select a block of text the selection won't hold long enough for me to copy or anything.

Edit: Having now gone to edit this comment, the arrow keys and mouse are working fine. But they stop working when I go to post a new comment again.

[fu]

Thanks; we umm made an embarrassing mistake, but it should be all good now. (Basically everything where there were issues with clicking after you'd opened up a quick reply was part of the same thing).

[ciaan]

And now that the cut-expander has been moved to the new JS... well, actually, it may do this in the old JS as well, I don't remember.... When I close it using the arrow at the bottom it leaves me looking at a point further down my reading page. It would be nice if I moved back up to still be looking at the entry I was reading.

[jmtorres]

Relatedly, I find when I click a link on my reading page and then come back to my reading page, any open cuts have closed and my position on the page is further down. I *think* it used to be that my reading page remembered what was open? Until refresh, I think.

(Also I am getting the "can't click earlier in the comment I am leaving to correct anything" problem reported by multiple here. I can arrow around in the comment, just not get anywhere with the mouse.)

I's on a Mac! Firefox 3.6.16, OSX 10.5.8

[fu]

Thanks, reported to the dev who's working on that bit!

[highlander_ii]

more on commenting:

When trying to select an icon from the drop-down box, the box doesn't persist, it rolls back up if you don't hold down the mouse button.


Also - selecting text - doesn't stay selected unless you hold down the mouse button. (just found this out trying to delete a line of text in this comment *g*)

[fu]

Hmm, I think that may have been part of some general problems with clicks -- should be fixed now, let me know if we missed anything!

[yvi]

The quickl reply on site scheme pages is doing the following for me:

If I click into teh subject field, the cursor directly jumps to the message field. I can't put in a subject.

[fu]

S'embarrassing and you've probably seen the cause in changelog! (Thanks, fixed *G*)

[yvi]

Firebug error on reply pages:

jQuery is not defined
jQuery(function(jQ){

Code:

247 jQuery(function(jQ){
275 var helped = 0; var pasted = 0;
276 function quote(e) {
277 var text = '';
278

[fu]

Oops, thanks, we'll have that fixed real soon.

ETA: fixed!

[lemposoi]

I'm using the Epiphany browser on Ubuntu 8.04. I just created a new post with a cut, and I notice that expanding the cut doesn't work. It appears to expand, but doesn't show the contents behind the cut. Cut expansion in my older posts works as it always has and if I click the post link, the contents behind the cut show up fine.

Just checked, same behaviour if I view my journal on Chromium or Konqueror browsers, too.

[fu]

Hmm, can you check whether it works if you turn off beta? that'll help narrow things down -- thanks!

[jana]

With the beta turned on, the (new) module 'Expand Cut Tags' tells me that there are "No cut tags" on a page. Beta turned off, I can expand all cut tags on a page.

OS: Linux (Kubuntu 10.4); Browser: Opera 11.10 (Build 2092)

[ninetydegrees]

Same thing for me on Windows 7/Firefox 4.0.

[zvi]

Windows XP, Chromium 10.0.etc

I'm on http://hooked-on-heroines.dreamwidth.org/9275.html in light style, and I don't have any expand tags, even though I'm a seed account. (If I switch to style=mine, I get expand tags.)

[fu]

Hmm. I see the expand thread links, I'm not sure what's going on! Are they still absent for you?

[jmtorres]

So the contextual hover menus aren't appearing for me at all--should I be getting the previous implementation of that?

Mac OS 10.5.8, Firefox 3.5.19 (and yes, Firefox, I KNOW, but it's not my computer to update).

[fu]

Nope, you'll only get the stuff that's been written new. (Otherwise you'd need to load a heckuva lot more data on the page, and that'd slow things down).

We'll have a contextual hover implementation come next code push!

[jana]

After the latest code push, I don't see any contextual hover menu when hovering over userpics. Still works when hovering over those tiny 'user heads' (the ones before a user name)

OS: Linux (Kubuntu 10.4); Browser: Opera 11.10 (Build 2092)

EDIT: This happens apparently only in my own journal style and when viewing a page/journal in light style, not when viewing a page/journal in site style.

[fu]

Hmm, I am not running into the same issue (using Chrome and Opera 10.63 on OSX)

Just to rule this out completely as a possibility (in case multiple accounts, etc), can you check your display settings to make sure that you've set the contextual hover to show up on both icons and the userhead?

[foxfirefey]

http://marahmarie.dreamwidth.org/107122.html

[secondsilk]

Clicking Top Level comments only takes you back to the first page of comments. This is very annoying.

I got through three pages of comments on top level only then replied to one. This brought up all the comments (so I could see mine), so I clicked on top-level only again, and was back at page one instead of the one the page I was on. When I clicked top level only after I had replied directly to the post, the same thing happened.

This looks like it's only a problem when I've commented (and therefore when the URL i'm on doesn't include the comment page number).

[denise]

That's not related to the new update page -- can you file a support ticket about that, so our support team can log the bug for it?

(whups, I just noticed this was a comment on the jquery beta, not the update beta. Still! It's a bug with the top-level-comment feature, which isn't connected to either. *G*)

Thread expander box positioning

[queenbarwench]

Late to the party as usual, but noticed that on some layouts, the thread expander is not positioning the comment boxes correctly. I'm not sure of the layout name*, but it's this page I'm currently viewing. I've seen it elsewhere, but I was on an old Firefox version and dismissed it at the time.

On to the bug!

Logged in (Firefox 8.0), I see that the top-level comments are correctly spaced (large gap to accommodate 50% of icon above the comment box), but I hit 'expand all' and boxes are close together with the icons of the child comments all overlapping the comment above. The top-level comments remain correctly spaced wrt the comment above. The same thing is seen when I collapse and expand a single thread.

I checked also in Chrome (15.0.874.120 m) logged out (hence no jquery) and the spacing was fine after expanding all. I logged in and expanded, and the spacing was compressed again. Interestingly, the collapse/ expand actions in Chrome place the icons *behind* the comment above.

Anyway, from my 2 second experiment I concluded probably a jquery-related issue, so here, have a bug report :D

(OS is Windows 7, btw. Just in case it still matters these days...)


* Random side note: might be nice to link direct to the theme page from the style credits box if it's a site style, for folks who decide that they like how others have decorated :)

Re: Thread expander box positioning

[fu]

Belatedly -- yup there was a bug, we're putting out a fix for it soon, thank you for your report (<3)

PS. we have a bug open for having the name of the theme in the styles credits box :D I even think someone may have claimed it, or at least is eyeing it with interest!

[boomvox]

Hello! I am on Windows 7 with Firefox 8.0.1. (Sorry about the RP journal, my personal one isn't paid, so...)

The 'Browse' button doesn't work when I'm previewing a comment. I can still change icons with the drop-down box, but hitting the browse button does not bring up the popup. Also, 'Choose random icon' is a text link in between two buttons for 'Browse' and 'Quote' everywhere - I don't know if that's intentional or not. It's fine, it just looks a little funny.

[nevertry]

i'm having the same problem on windows xp with chrome. :3 (LOL HI, WE'RE NERDS, ALSO)

Unable to cancel reply, unable to distinguish buttons belonging to original comment from reply

[noracharles]

I tried replying to a comment I had made myself, just so I could see if the changes I had made to the font settings in my browser were working. I didn't want to post the comment, it was just gibberish to see the font.

I could not make the comment box go away again, not even when I tried reloading the page.

I had trouble visually telling the buttons belonging to the original comment and the reply apart, and ended up accidentally deleting the original comment (made by me) because I thought/hoped I was hitting the "cancel" button.

I'm using my own style and Opera 11.60 build 1185.

I must be remembering an older type of reply box, because this behavior is the same whether I have the new JS behavior enabled or not. Sorry about that.