Mark Smith (
mark) wrote in
dw_maintenance2012-09-22 08:37 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Code pushed
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!
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!
no subject
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.
no subject
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.
no subject
(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.
no subject
no subject
no subject
#menu => nav
#sidebar => nav
#footer => footer
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
In Firefox via greasemonkey/stylish. I don't know about any other browsers, I'm sorry. Also, if you have the new comment pages beta turned on, some of the colors will be off still.
no subject
Thank you! I have my lovely blue scheme back! Thanks so much!
no subject
/**
* EDIT FOR S2 COMMENTS BETA
*/
.comment-wrapper-odd .comment .header {
background-color: #bbddff!important;
border-bottom: 2px solid #bbddff!important;
border-top: 2px solid #bbddff!important;
border-right: 1px solid #bbddff!important;
}
.comment-wrapper-even .comment .header {
background-color: #aaccee!important;
border-bottom: 2px solid #aaccee!important;
border-top: 2px solid #aaccee!important;
border-right: 1px solid #aaccee!important;
}
.entry .inner .header { background-color: #ffffff!important; }
no subject
(no subject)
(no subject)
no subject
no subject
#page a:link,
.link {
color: #575271 !important;
}
#page a:hover,
#page a:active,
.link:hover {
color: #746ea4 !important;
}
body.tropo #canvas #content {
margin-top: 2.75em !important;
padding: 0 !important;
width: 100% !important;
font-size: 9pt!important; }
body.tropo #page { max-width: 100% !important; }
#page_talkread #Comments .talk-comment,
#page_inbox .InboxItem_Content {
max-width: 100% !important; }
#page_talkread #entry {
max-width: 95% !important; }
no subject
no subject
Here's the full code, I don't think anything overrides them:
(I saw the note that most div.foo were changed to nav.foo and I tried replacing all the .divs in the code with .navs but that didn't change anything.)
no subject
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject