Code push has happened!

[mark]

Hi all, I'm preparing to do a code push. You can see the latest code tour here: https://dw-dev.dreamwidth.org/214638.html

Hang on to your hats!

Edit: The code has pushed! As always, please let us know if you see anything wonky or broken and we'll get on it!

Known Issues - Fixed 'em Maybe?

* Font size was way too small. We've tweaked them to be larger, but would welcome more feedback!
* Lack of ability to horizontally resize comment area. This has been fixed, you can drag the box horizontally again like you should be able to!
* A couple of style issues have been found and fixed.
* An issue affecting some Navigation strips has been fixed.
* An issue affecting syndicated accounts, proxied images, and a couple other worker related tasks were broken. They're better now.
* We've made some updates to the design of the comment reply form, we brought back the browse button, made the subject line full-width, and some other tweaks. Please let us know what you think!
* The RTE on the old create entry form is returned to service. A few more months, that's all we ask of you old friend...
* OpenID was broken, it's back.
* Button sizes are reset to default, we are no longer trying to make things line up. Let the ziggurat design pattern live on.
* Polls should show properly sized bars again.
* Lots more Android issues, we had to murder the unused spellcheck button to make it work out. Some weird interactions with differently sized elements and our ancient HTML.

Known Issues - Pending

* Related, some fields seem to have gone emo and are putting on heavy eyeliner (have bold, dark outlines). We're aware.

All known issues are being investigated and will be fixed! Please hang tight while we work on it :)

If you are reporting something visual, please let us know what browser/device you're on!

Comments

Re: That at-sign expansion at entry display time

[roadrunnertwice]

Most markdown implementations automatically escape otherwise problematic characters when they occur in code spans and code blocks. If we’re doing the username conversion after things arrive in HTML land, we probably need to make sure we’re excluding them from a similar set of elements — <code>, <pre>, possibly <textarea>, though wow, that one wouldn’t have occurred to me until today.

Re: That at-sign expansion at entry display time

[pauamma]

Hmm. I guess that solution would work in most cases, and if Afuna can live with https://afuna.dreamwidth.org/535807.html still being mangled (which I think it would be), so can I. I'll miss not being able to say "my dreamwidth email address" in entries and comments without some additional effort, but maybe I'll get used to that.

Re: That at-sign expansion at entry display time

[denise]

You can quick-escape by sticking a \ before the @, btw.

Re: That at-sign expansion at entry display time

[pauamma]

Yeah. Experience will show if I can remember to do that in time, going forward.

[saga]

I can definitely confirm that yesterday I did see it occur in the < code >, but it appears to look like @ now such as here https://developmenthell.dreamwidth.org/1387.html i'm not sure if I can work in CSS custom boxes yet since I only just looked. Thanks!

[denise]

We put in exceptions for CSS at-selectors this afternoon, yes!

[saga]

YAAAAAAS thank you so much!!

[pauamma]

Are you planning to put in exceptions for entry and comment content inside <code>...</code>, <pre>...</pre>, and <textarea>...</textarea> too, as mentioned in https://dw-maintenance.dreamwidth.org/78131.html?thread=3030835#cmt3030835 ? That would be great.

+1

[saga]

I agree with this as well; while it works for font_face and media now because they're exceptions, it would be great if every other @ call can remain looking like @username instead of calling it. I tried them out here: https://tofuhouse.dreamwidth.org/5879.html and since using textareas and codes are popular in coding communities, this might become a big hassle in the future.

Thanks for looking into this too, team.

Re: +1

[pauamma]

And another exemption is probably needed for content (or at least entries) in syndicated accounts.