Mark Smith (
mark) wrote in
dw_maintenance2020-04-26 01:27 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 has been pushed!
Hiya, as per yesterday's announcement, the latest Dreamwidth code has been deployed.
This is the issue/bug/problem tracking post! Please let us know if you see anything... untoward.
Fixed
- Posting an entry would tell you that your password was blank.
- API key generation/deletion was... behaving a little weird.
- Profiles pages were converted to Markdown, but this was too soon. I've put them back to raw HTML, they should look like they did before the push!
Known Issues
- Chrome auto-filling in password forms, when trying to post as the already logged in user, results in an error. Still haven't fixed this one, but we will.
Reports of logging out possibly not? Need more information, login/logout work for me.Seems transient?
And as a reminder, if you use Semagic et al, please check the link above for information on how to configure it to keep working with Dreamwidth!
no subject
Also, is that white starburst in the left-hand corner (to indicate browsing, maybe?) really necessary, given that you also have the word 'browse' over the default icon?
no subject
No clue what the starburst is in the left; it's not something we're doing deliberately. Possibly another Safari glitch.
no subject
I'm assuming you've seen what it's supposed to look like with the new update, so here are the problems I'm seeing (of which we might fix some, but probably not all):
- "More options" is in the same row as the username. Expected behavior on old browsers that don't understand CSS grid; I put the controls in an order that makes sense specifically so it'd still be usable, even when it doesn't look as good.
- Icons drop-down menu is below the icon preview instead of beside: same deal.
- Starburst in the corner of the icon: Okay, that one's pretty bad. I'll have to see if I can fix that. We're drawing a shape and positioning it so it goes behind the word "browse," so the browse button is legible; idk why it floated off to Mars for you. Probably the meaning of the positioning arguments changed.
no subject