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

[snickfic]

I think somehow at least one of the image formatting tags is now broken? The height tag (eg height="300") no longer has any effect, and images with that tag are now displaying as their actual image sizes, but the width tag still works fine. Also, all images inside tables seem to display as the size now, much smaller than either their actual image size or as determined by the height or width tags.

[denise]

Can you link to something that used to work and is messed up now?

[snickfic]

If you go here and ctrl+f to "five years younger than Noel," the three images that follow were all the displaying yesterday as being 250 pixels high. There are a bunch of other examples in that post as well.

[roadrunnertwice]

So! I think this was already happening on journal-styled pages before this push (in journals that didn't use a completely custom style), but now it also affects site-skin comment pages. Does that match what you've noticed?

Previously, we added code to shrink images in entries and comments to make sure they don't break peoples pages. (We did that so people can easily post images without worrying if it'll blow out everyone's friends list or make a mess of the thread.)

But initially, that code lived in specific journal styles. Now it affects all comment pages, including site skin ones.

For images standing alone, you can fix the problem by specifying both height AND width in the image. (Or just width; height is kind of special, it's complicated.) I know that's more work with a calculator, which is a bummer, but it's the cost of making things work better for the more common case.

For tables... images shrink to fit their containers these days, so if the table is small, the image will be small too. You'll need a bigger table to get a bigger image.

Two other bits:

- You can take advantage of the fact that images shrink to fit their containers, and put them in a container with a fixed height. For example, <div style="height: 250px;">...</div>.
- Images that AREN'T also links now get a "click to zoom" behavior, with a special mouse cursor showing when you can use it. So if an image shrinks too small, readers can opt into seeing the full size.

[snickfic]

Yeah, that matches what I've seen. Thanks for the tips.