Code pushed

[mark]

Hi all!

We've pushed live the latest code for Dreamwidth. There are some major internal changes to how we serve up files, so you might see some things being a little weird. Please report anything that isn't loading, looks broken, or what-have-you!

Thanks for your patience!

Comments

[widowmaker]

Those of us using custom skins to make the site more functional/visible for us in ways that aren't covered by the official skins are finding that most of them are pretty borked now. Is there anything you can do about that, or should we just go make sad eyes at the people who made the overrides?

[eyesofstrength]

I noticed the same thing! Looks like this for me now and before it looked like this

I know we have to edit the style in Stylish or whatever is being used, but I have no clue what to even edit or look for and what it is now and viewing source was of no help to me.

[denise]

Ugh, I hadn't even thought about Greasemonkey custom site skins, or I would've made it clearer ahead of time that things would probably break. Sorry :/

We switched our site skins over to using some new features of HTML5 for better accessibility for people with disabilities and to take advantage of some new features in the HTML spec. The biggest change is that classes that used to be styled by using "div.foo" are now mostly addressable by "nav.foo". It's the sort of thing the person who made the custom site skin will have to fix, yeah.

[widowmaker]

I suspected something like that might be the case. :/ Thanks anyway, I'll forward the note and cross my fingers.

On that note, though, is there any hope for having a proper site skin with wider width and more contrasting colors? The skins you guys have are great, but it's not a catch-all for everyone with vision impairments; the grey and the soft purples and pinks actually make it harder for me to see (I have vision and neurological issues) and I know I'm not the only one, though definitely in a minority.

[isana]

When I was posting a few minutes ago, the random icon option wasn't there.

[denise]

Hm. I see it there in all my browsers; do you mean on posting or on commenting?

[glampuss]

I just edited a post of mine, and the "Save changes" button didn't have any text:



Clicking on the blank button did save successfully though, and when I went to edit the post again the text was displaying properly, so that might have been a one off thing or something.

I am finding that now that I've edited that post, the "disable auto-formatting" setting that I had for the post has now turned off. I can't seem to find how to turn it back on - is that option still available?

[isana]

When I was making a post, but it was a few minutes ago, and I see random icon right now when posting a comment.

[mark]

The "save changes" text should be back now!

We will investigate the other thing, re: formatting!

[marahmarie]

My comment titles are borked. I'd post a screen cap but I haven't attempted to fix them yet so you can see them borked live if you like here: http://marahmarie.dreamwidth.org/139790.html?nc=3#comments fixedit


I'm pretty sure it's new CSS classes added during code push or some-such thing at fault so I won't worry about it unless I see I can't fix it; just thought I'd give a heads-up. the addition of HTML classes .comment-from-text and .comment-date-text, along with the apparent re-confoobling of some comment title positioning aspects, led to my mess on those pages; hid this, changed that, all fixed now

[onetouchdonnie]

I really like how smooth the whole code push was! Didn't realize until Mark posted it here. Great job everyone~

[denise]

The text missing from the button should be fixed now -- we'd missed running the script that updates the text on the site.

The "disable autoformatting" thing is a bit more involved -- we do intend for the new update page to have that still available, but we've been arguing about where to put it, so it's not implemented quite yet. For now, if you need to disable autoformatting, you can temporarily turn off the beta update page (the second of the three options), or surround the bits that shouldn't be autoformatted with <raw-code> and </raw-code>.

[glampuss]

It was there just then, so looks like it! Thanks!

[tameiki]

You know what I love best about these code pushes? It's how you not only spring into action to fix whatever got borked, you also take the time to explain things before, during and after you fix it.

That always makes me smile. Thanks for all you do!

[glampuss]

It hasn't disappeared again yet, so it looks fixed to me!

I think for now I might need to go with the "raw code" option, since if I switch to the old one to turn off auto-formatting, once I change back to the new version it looks like any time I go and edit the post again it turns auto-formatting back on. ...yeah I know I could just keep using the old update page, but I just really like the new one okay

I am glad it'll be coming back sometime though, it's a feature I really like!

[juliet316]

I'm not seeing the little Dreamwidth icon in my window tab/address bar. Using IE.9

[fairandbright]

I noticed the icon browser has changed on another account I have that is paid, and it seems less useful now. If I select small images w/ no meta text, there's only three icons to a line, with blank spaces where the meta text would go. It used to be they lined up right beside each other and there were a lot in a row (not sure how many, but at least 10?). Any way to fix that so the icons line up together again when I select small images and no meta text?

[musyc]

The favicon is having some fluctuation. I can see it on reading/journal pages, but it's missing on some site-scheme entry pages. This entry, frex. Firefox 15.0.1, Win 7.

Noticed as well: The yellow warning banner telling me that I'm using the new entry update thingummie beta - the edit entry thingummie beta that has appeared (yay!) still says "create entries" and is missing the username for dw_beta.

[denise]

The problem with adding additional site skins is that there's really an endless combination of accessibility needs. We've tried our best to hit the major needs (high contrast vs low contrast, dark-on-light vs light-on-dark, horizontal vs vertical, etc) but there's always going to be at least one person who they don't work for :/

(Limiting the text width in the Tropo site skins is one of those things, for example -- for the vast majority of people, a long unbroken line of text is much harder to read, and it's only a small minority of people (you among them, apparently!) who find that to be more of a problem.)

We have talked about ways to make site skins more customizable on the user end without having to resort to Greasemonkey scripts and the like, but it's the kind of thing that's really hard to do well. It's not something we've ruled out entirely, but making it possible would be a whole lot of work and would have to be really carefully designed to not overwhelm people with options. So until we can work out a good solution, the best option is to use Greasemonkey to make whatever tweaks will help with your accessibility needs -- we really don't change the site skins very often, and only when there's clear benefit, so it's not like those tweaks will break often.

[marahmarie]

It's missing from Maintenance, yeah. But it was missing before the code push, too (seriously, thanks to another journal error that I've figured out, I've been here all night).

[widowmaker]

Haha, yeah, I know I'm way in the minority. Unfortunately that doesn't make it any easier for me to see stuff when my brain decides not to process it. Thanks anyway though, I'll just keep hoping it happens eventually.

disable autoformatting

[pne]

I am glad it'll be coming back sometime though, it's a feature I really like!

Ditto!

[sara]

It would be really nice if y'all would teach the github account to cut-tag at some point. My network page is all hard to read (yes, on the scale of Actual Problems this is pretty trivial.)

On a related note, its icon cracks me right up.

[silvermoonshade]

So, I was posting to a community under a different screen name for a game, and decided to preview it to see if I liked the look of what was posting and instead my personal/real journal popped up in the preview window as the journal making the post and not the fake/ game one.

[denise]

I'm sorry I don't have better news!