Code has been pushed!

[mark]

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!

Comments

[roadrunnertwice]

Ha, woof. OK: tl;dr: set flex-shrink: 0; on the div that has the image in it.

There's a lot of gotchas to making display: flex stuff size the way you want it to. In your case here:

- You've set a width for the flex-item div that contains the image: ok, cool! IIRC that becomes the default flex-basis for that flex item. That's its starting width.
- But flex-shrink defaults to 1, so if the contents of that div don't push back, the other flex items can steal space from it.
- The global image shrink CSS makes it so images can't push back on their flex item parents; therefore that flex item goes tiny.
- But if you use flex-shrink: 0 to say this flex item can't be stolen from, then you're fine and the image will fill the available width.

Here on DW, the image might still shrink a bit if someone's browser height would be too short to display the whole thing. But that's what the new click-to-zoom thing is for.

Anyway, keeping an eye on flex-shrink should serve you well everywhere; hopefully that also clears up how it interacts with the image shrink thing.

[roadrunnertwice]

This post dedicated to all the hours I spent debugging this exact same behavior trying to keep userpics from shrinking to chiclets in the updated site skin comments CSS.

[maximite]

Excellent, thanks for letting me know! I wasn't sure what the gritty details of the coding interaction would've been to cause that, so the extra info is very welcome (also whoof I do not envy you having to figure that out on the userpics, that sounds like it would've been quite the time)