Quick push

[fu]

Just did a quick push for the various (mostly styles-related) issues that people brought up in the previous dw_maintenance entry. Thank you to everyone who let us know when you noticed something had changed!

(PS thanks to all the devs, especially the indefatigable ninetydegrees who were right on top of the changes).

Comments

[pickledginger]

Thank you!!

[fu]

*cough* ignore previous comment please. Replied to wrong thread.

[twtd]

I haven't checked this on my computer, but on my iphone all of the cut tag arrows have changed into icons. They still expand the way they're supposed to and I actually like how they give me a bigger target for my thumb, but they do look a bit odd.

[fu]

Hmmm, that sounds like caching issues. That is, we haven't changed the image, but it sounds like your iPhone is for some reason using a different image rather than the one we're using. Can you try clearing out the cache? It should be in the settings for Safari.

[twtd]

Clearing everything didn't fix it, but restarting my phone did. Thanks!

[bluiis]

You guys always do an awesome job!

[pikabot]

Over the past couple of days I've noticed some strangeness with some comment pages. It seems to happen at random, but when it does no amount of refreshing will fix it.

Basically the big white bar with the Dreamwidth logo in it is covering up most of the rest of the header. like so. You can see the top of my default userpic poking above it there.

The elements are still there, just hidden behind the white box - I know because you can still access them by tabbing, I had to log in on my phone that way earlier.

[fu]

That sounds like mismatched HTML. Can you link us to specific pages where it's happening please? Thank you!

[pikabot]

this is the only one I actually remember, haha, although I've seen it elsewhere.

[denise]

Yeah, that's definitely mismatched tags! Go through the entry and count all opening <div>, <table>, <td>, and <tr> tags and make sure they're paired with closing tags.

[momijizukamori]

I can toss you two other examples if necessary, Fu. It looks like the HTML cleaner isn't closing unmatched div tags properly for some reason.

[denise]

The HTML cleaner isn't really trying to close mismatched tags -- it doesn't know where they should be. People just have to count up their <div> and </div> tags carefully :P

[momijizukamori]

Hmm, well, something closes mismatched tags - I experimented with leavingan open bold trash, and it doesn't mess up the rest of the page

[marahmarie]

Is that in RTE? In the HTML editor I normally have to close/match every tag except paragraphs or all hell breaks loose.

[momijizukamori]

Nope, HTML editor. It'll mess up the rest of the entry text, but the problem doesn't overflow into bolding the comments or any of the style elements. I actually just inspected it with firebug, and there's a closing bold tag that I never typed in, at the end of the entry.

[marahmarie]

Oh, you mean leaving a tag open doesn't break the whole page, like the comments, et al. DW has (the last time I checked with W3C; I'd have to check again to see how extensive the problem is and exactly what page views are still affected) a single unclosed div on entry/reply pages... Possibly that is hiding the problem? *otherwise clueless as to why page does not break*

[afuna]

Hm. We do make a best guess effort but sometimes really mismatched tags can defeat us. If you could pare it down to the very minimum that can cause this issue please forward it to me <3 fu@dreamwidth.org is fine!

[momijizukamori]

I'll see what I can do about a minimal test case :) I think the big thing is that these were all sets of code that worked fine before the code push and then some change we made borked them all up

[fu]

Huh I hadn't realized those worked before! Can you open a bug for that please? Let's continue there so the investigation can be more visible to others interested.

[momijizukamori]

Hmmm. I'm not sure what I should file it under? I'm also having a hard time with a minimal test case - I only have really complex sets of code and breaking it down isn't yielding the same results.

[denise]

It's kind of on the line between Misc UI/Frontend and Site Layout/Navigation, but I'd probably put it in the former. If you can't get it down to a minimal test case, post the complex sets, or post to dw-dev-training and see if anybody wants to help poke at it with you?

[momijizukamori]

Roger that o7

[denise]

<3!

(could also go in -dev! or -volunteers, even. up to you!)

[doldonius]

The unclickable entry title glitch seems to be still there, I'm afraid :(

[fu]

Hmm, oh yes that one! Easyread, right? We're currently trying to decide how best to fix it (the easiest fix would also affect how the content is presented to screenreaders, so we'd like to avoid that as much as we can)

[doldonius]

Yep, Easyread. No worries, though, setting title size to 2 still works (in case somebody else runs into it.)

[darkicedragon]

\o/ Thanks!

[lannamichaels]

It seems like in the last push (earlier?), the post title changed its format slightly in the Celerity site theme. I can tell it's different, but I cannot pinpoint exactly what changed. I think my lack-of-noticing-visual strikes again.

[afuna]

Hm. I think we either made it a link or tweaked it to be simpler codewise which might have affected the spacing slightly.

[deadlyjuliet]

Just noticed this, but the comment box for all of my accounts has been shrunk to about half it's size; this for example.

Also the font is extremely small; seen here and above. It's only effecting DW comment boxes and unless I scale Mozilla Firefox 13.0.1 up to it's fullest zoom, I can barely see the letters.

Any suggestions?

[denise]

Can you check in Firefox's settings and tell me what the default font and font size is for monospaced fonts? (I think I remember Firefox being very stupid about that somehow, and most sites try to compensate for it by overriding browser behavior but we don't, because it's an accessibility issue.)

[deadlyjuliet]

Hey Denise, looks like the default font and font size for monospaced is: Arial, minimum of 10, default is 10. I went in and switched those to a higher size and now it seems to be working better. I wasn't even aware that Firefox did that. orz Thanks.

[denise]

*nod* Hopefully that won't cause problems too badly with other sites that try to compensate for things! Firefox tries to set text declared as monospace to smaller by default (because monospace fonts are perceived as larger by the human eye), so if you use a non-monospaced font for things declared as monospace, it can wind up looking really weirdly small!

[moontothetide]

I'm having some weirdness with my userpics - it seems to only be on this journal. But, when navigating, my default userpic doesn't show up (it just has a link with "upload icon"), and on my reading page, there's this weird mush of black bars with my alternate text on them. Is there anything that can be done to fix this?

[denise]

That usually means your browser cached an old copy of the page where things didn't load. Try clearing your cache and reloading the page.

[hickumu]

That seems to have done it! Thank you very much :-) .

[denise]

You're welcome! Glad it worked :)

[mewsing]

I've noticed the last couple of times I've gone to import comments from my Livejournal, instead of the importer adding the LJ comments to the original DW posts like it used to do, the LJ cross-posts are now getting imported as duplicate entries. Is this normal?

Correction: on some of them, it has added the LJ comments to the original DW posts, but also imported the post from LJ as a duplicate with no comments at all. Appears to be totally random. I guess I'll stop using the importer to import comments from entries that are cross-posted on LJ, cos I don't want double-posts of everything. That is a huge bummer, cos I liked being able to mirror everything here, including comments. :/

[denise]

If you're 100% positive the entries were absolutely posted through the crossposter on DW, open a support request for that, with links to both a pair of entries that imported properly and a pair that were duplicated (it will take a while for a response, since those are very complex systems). (If there's a chance the entries were copy-and-paste posted, mention that too: the importer isn't quite *that* smart *g*)

[mewsing]

They're definitely being duplicated from LJ to DW, as the extra posts have the footer "➤ this entry was originally posted at http://mewsing.dreamwidth.org/376499.html" on them. :(

Do these entries I link to need to be public? I tried to import comments again this morning and got duplicate posts again (after deleting most of the duplicates yesterday) and no comments imported even though the message in my inbox said it was successful. It looks like instead of importing LJ comments and adding them to existing DW posts (originally posted on DW), it's importing the posts (cross-posted from DW to LJ) themselves without comments. I may just give up on importing comments to DW if it's going to be a pain for you guys to figure out what's happening. I know y'all are busy.

Thanks for the reply!

[denise]

No, they don't need to be public, we'll just need the itemids in order to dig into things. We might not be able to figure anything out, especially since you're the only person who's reported the problem so whatever it is is likely going to be really hard to reproduce, but please do open a request (especially so the information will be there in case anybody else *does* report it)!

[mewsing]

Understood. :)

Here is the request:

http://www.dreamwidth.org/support/see_request?id=16943

Thanks again!