Code push has happened!

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!

Flat | Top-Level Comments Only

*double-checks code tour* isn't the point of 2486 so this won't happen? Chrome on Android.

YES, but alas: that improvement doesn't affect the site-scheme entry pages, because they're too different and bizarre and non-mobile-ready.

I want to make those not suck, and the issue for that is 2427, but it has some hefty prerequisites (which are, at least, currently in progress). Sorry.

feh.

thanks!

On the importer, I've been stuck on Verifying username/password - Ready to be entered into the queue for the last three hours or so. It's not failed or anything, just sits at that initial stage. Could that be a result of the code push?

Some changes were made to the importer -- I will flag this up.

Thanks very much, really appreciate it :)

Hi! Imports should hopefully be starting to move again. If you've not seen any progress in 15 minutes, can you please let me know? If so I'll bring this back to the site admins!

It completed about 30 minutes ago for both journals, thank you so much!!

Fantastic, thank you!

"Post an entry" only offers an HTML window, and won't let me switch to Rich Text.

[My Dreamwidth settings are to Rich Text. I've tried switching my settings back and forth a few times, logging out and logging back in. It doesn't fix the issue.]

Thanks for the report! The RTE is very old and cranky at this point, so I'm not surprised something broke. We'll do what we can to get it fixed (until we can replace it, which is the long term goal that is not gonna happen today, heh).

My biggest issue here isn’t so much the font or the hecked up buttons as it is the lack of a dev environment. Many of these problems wouldn’t have happened if the team had counted with a testing site/localhost server to actually see wtf their code is doing. I really appreciate the job you guys do, but please try to fix this for the future as this was a totally unenjoyable experience.

Thanks! We do test things repeatedly (both using automated tests and manual/visual tests) while we're working on them, and these particular changes were tested by multiple people with different systems/devices/browsers. It's not feasable for us to visually test every style and theme on the site, though -- there's a lot of them, well over a thousand last time I checked -- so the sort of issues that don't get caught by automated testing will always sneak through. And although we aim for as wide a variety of systems/devices/browsers in testing as we can, everyone who visits the site has a slightly different setup due to browser version, browser settings, extensions installed, etc, so any design or CSS changes inevitably need a bunch of after-the-fact fixes when they meet the real world (much wider) set of configurations.

I'm sorry for the hassle! Ultimately these changes are to modernize a bit of the code that was really, really old and janky so that we can support mobile browsers better, since usability on mobile (and other small-viewport devices) is people's #1 most-cited issue right now. But, because the code in question is literally 20 years old and had layers and layers of "wtf" lurking in it, we had to strip it down pretty far to make any progress and then rebuild on the new bones, so it'll take us a few rounds of fixes to shake out all the issues that only show up once changes hit the real-world panopoly of people's configs. We will get it all fixed!

Thank you so much for your response, and I appreciate it a lot. I totally understand what you're talking about and I apologize if I was rude in my last comment because boy oh boy legacy code is....something, alright.

Good luck, team!

THE CODE SURE IS SPECIAL, ALL RIGHT

But yeah, we've sort of hit the point where we've done what we can do to achieve better mobile usability just with minor tweaks, so now we've gotta get our fingers into things and really dig. It's like how if you're trying to tidy up a room that's full of unorganized stuff: sometimes you have to pile everything on the floor first in order to organize the shelves. And then skip through the piles of stuff figuring out which of the things truly ~~spark joy~~ need to be there. ...I may have been listening to too many people talk about KonMari lately.

Anyway, these particular changes didn't show any of these issues in testing! But we have so many styles and people use the site in so many ways and on so many devices that any major frontend change is inevitably going to produce a Giant Problem when the code meets real-world conditions. We'll get it fixed as soon as we can!

Hello! This isn't an issue so much as a request. Please bring back the Browse option for paid accounts. A lot of people who use DW for roleplaying games greatly appreciated the functionality of being able to view all of them once in order to make their selection. And as the DWRP community is one that spends a fair amount of money on icon space for their various RP accounts, I worry that taking this away will cause an unnecessary amount of unrest and discontent.

I see that you've stated "We are going to bring back the browse button and move a few things around to address some of the feedback people have provided.", so I am not too worried that it may be gone forever. However, I hope that this will be sooner rather than later. Thank you very much.

If you click on the user icon next to the comment, you can view all of your icons. Should be able to, barring using the DWTools Chrome Extension.

Someone on Plurk just pointed that out to me. It would be preferable for it to be labeled alongside the icon rather than only when hovering or clicking on it, though. Most people would not think to click on or hover their mouse over that image without first being told, making it counterintuitive. So like, if the 'Browse' word got moved from the image's hover-function down to right below it so that it's always visible, I think that would prevent users from overlooking this. Thank you.

Hi there!

This is an issue the dev team are aware of; it's on the list to be looked at as soon as they've woken up (they're mostly in the US) and had enough coffee (or food, or hydration, or other nutrient) that they're reasonably confident they'll make things better, not worse. Apologies for the inconvenience, and thank you for bearing with while this gets sorted!

I've had an issue for MONTHS on mobile (I use chrome on Samsung Galaxy 7/Android device, can check specifics as needed.) where when I start typing in the text box to reply, it stretches the comment field out to where it overlaps the buttons. I've literally been working around this for months by uh... turning my phone orientation before I post a reply to make it where I can hit the buttons again. If this isn't a known issue I would be super happy to provide screenshots and info! Just let me know what you need~!

Is it still happening? Last night's push contained a fix that I think may fix that issue. Otherwise, screenshots and device/browser specifics would be great, thank you!

Yep still happening!

Visual
Chrome version
Android 8.0.0 on Samsung Galaxy 7!

It's not like I'm not used to it but it seems to be impacting more people now! Thanks for looking at it!

Thanks! We'll see what we can do.

quick comment to +1 and say that this has been happening for me pre-code push (samsung s7 and samsung s9) and also had to do the phone orientation trick (on chrome). Sometimes it'll stretch the box over the buttons, sometimes it puts the text under them.

I think it also used to do it on Samsung's browser but a test comment seemed to not have the issue.

I think that one depends on https://github.com/dreamwidth/dw-free/issues/2427, because I've only ever seen shots of it on the site-scheme entry pages.

Right now, I suspect the best way around it is to enable the option to view EVERYONE's comment pages in your own journal style, and pick a style that currently works well on mobile. We're working on fixing it on site-scheme too, it's just... some hairy code.

I can give it a try! Thanks for the response

Headers on my communities seemed to have all disappeared abruptly. 8(

knightsoflegend

drakenet

theround

as well as on individual journals, etc. Other friends are reporting the same.

Headers on multiple journals of mine are now missing;

morethanasidekick

gwenbloodycooper

(There's many more but these are a couple of examples)

Other journals have entries with images that were working fine, no longer displaying like in this entry

Note: Using Google Chrome on a Windows 10 PC

Edited 2019-06-23 15:18 (UTC)

Thanks, we will try to narrow down the problem and fix it! For the two journals with the headers missing, which themes are you using on them, and do you have custom CSS on either/both?

Both use transmogrified with custom css. I do have another journal with transmogrified and custom css that's fine however:

littledhampir

This should be fixed now! (It was a problem with the image proxy.)

For reference, the code used is below:

Just to clarify, when you say 'header', you mean a header image that you added to the layout, right? (Just want to make sure I'm looking at the right thing!)

Yep! When you go to the comms now, there is just a thick beige strip where it used to be.

Thanks! Just wanted to make absolutely sure that I was looking at the right thing. :)

While I was poking at it a bit to see if I can figure out what's going on or if it's something that'll have to wait for the CSS experts to weigh in: I do see a header image on knightsoflegend, but drakenet and theround don't have it loading. Do you know off the top of your head if all three accounts are using the same theme? (I'm *guessing* something in the theme is conflicting with some CSS and the image is winding up thrown into the background behind the page's background color, but that's just a guess -- it could be due to other things.) Also, do you have any custom CSS entered that's different between knightsoflegend and drakenet/theround?

(The other thing I can think of that it might be would be more of a pain for us to fix, so I hope it's that, heh.)

The header image does not load on my screen for knightsoflegend (I use Chrome) or on some friends' that I had check it. I use the same CSS for knightsoflegend and for drakenet, but with two different header images.

The Round just uses the Neutral Good theme, and then has the header in the "Images" section under "Header" as a link.

Thanks for any help you can give! <3

okay, that's officially Weird, then. We'll see what we can do! *

* I say 'we' but really I mean "the people who know what the heck they're doing with CSS", which is definitely Not Me, heh

Okay, this should be fixed now -- it turned out to be a problem with the image proxy that we use to load insecure images securely.

You guys are heroes!! Thank you so much! ♥

I don't know if it's been reported yet, but:

When you comment on a post that's at captcha and you're redirected to the captcha page, the icon you selected to go with the comment reverts to default. Only way to change it back currently is post the comment and go back to edit it. Using Chrome.

Hi! To help the dev team narrow down what's going on, can you please confirm what type of CAPTCHA you're seeing? You should be being shown one of text-based (a logic puzzle, e.g. "What is Mark's name?") or image-based (e.g. pick all the images containing a bus).

It’s a text-based captcha.

Thank you - that's exactly the information I needed. Devs are looking into it now!

Found the fix for that one! It was weird. Should go live soonish.

The user tag is messed up for for AO3.

I used to be able to type <user name=OldToadWoman site=ao3> and it would display with a nice clean link and a tiny AO3 logo, but now it's displaying with a broken image and "[archiveofourown.org profile]".

testing:

OldToadWoman

Thanks, we'll see what we can do!

Thank you for this report! The dev team have worked out what was going wrong and site admins have now fixed it.

Awesome! Y'all rock!

This should now be fixed, thanks for your patience!

Fantastic! I love that y'all fixed this in under an hour and are still thanking me for my "patience". ♥

Technically, it was broken since last night, you're just the first one who reported this particular symptom of the same root cause. :)

I imagine you're playing whack-a-mole with a lot of error reports right now. ::sending virtual coffee::

I love this website and just want you all to know how much I appreciate it.

Thanks! Not gonna lie, for some of them we've been looking at it and sobbing "but we didn't CHANGE THAT HOW DID IT BREAK", but we'll get 'em knocked down one by one. :)

did RSS feeds go wonky? I'm not seeing updated posts on my reading page...

They are! However, workers are about to be restarted, so fins crossed this'll be sorted Imminently.

This should be fixed now, let me know if it isn't!

hello, is it normal that since the code fix I do not get predictive text for tags in a group I'm in?

Thanks for flagging this up - it's not supposed to be happening but I suspect I know (roughly) what's gone wrong. I've flagged it up to the dev team.

just discovered it isn't the case for every group, just some of them. fffc was affected, drabble-zone was not.

Is one of them using the beta update page and one of them using the old update page?

not sure how to tell, but the others just started working again, oddly enough

mark just made some changes that probably account for that! Thanks for giving us the heads-up.

When posting an anonymous comment (while logged in) and answering the text-based captcha, I fill out the appropriate answer, press "enter," and instead of the comment being submitted, the icon-selection screen pops up. It submits fine if I click "submit," though.

I'm using Firefox 67.0.3.

Edited 2019-06-23 17:50 (UTC)

... thank you so much for flagging this up -- this is the problem that's proving trickiest to debug so the extra data is very much appreciated, even as we sit here going "... I... HOW."

I also got that, and I'm on Chrome 75.0.3770.100 (it just updated).

No icon choices when creating an entry. Using Firefox on an imac. The good news is Rich text is now working. Thank you.

Thanks for flagging this up! I'm very confused about what's going on but I'm in discussion with the dev team.

Size is okay for me (desktop with Firefox and Chrome), but no matter what sort of threaded comment I'm replying to, the comment box always opens in the very center of the page. This makes it really visually disruptive when you're trying to reply to a comment that's all the way to the left side of the page. They always used to open just slightly to the right of whatever you were replying to, which made a lot of sense and didn't require so much back and forth eye movement. Not a fan.

Edited 2019-06-23 17:59 (UTC)

Thanks for letting us know! I've flagged this issue up to the devs.

Thanks! Also, it seems to be more of a problem when viewing in the "light format" as opposed to "original style" - in the light one it opens more to the right of center and the text is a bit smaller.

Hi! Are you seeing this on any "journal-styled" comment pages, or just on the "site scheme" and "light" versions? I think I'm seeing what you're seeing, and it looks like a CSS fail specific to the site and light ones, but I want to make sure I'm not missing something.

Edit: Yeah, I think I found the problem -- the problematic code was aimed at every page, but it was only HITTING the site and light ones.

Edited 2019-06-23 19:06 (UTC)

I think those are still centered but the different styles sort of expand each comment area so you can easily tell where you're commenting b/c it's all within a colored box:

That seems fine. Also yay, it's working on the light style now! Thanks.

ETA: That uploaded super tiny, so I'm sure it's no help, but as all seems well now I'm not gonna worry about it.

Edited 2019-06-23 19:33 (UTC)

You embedded the thumbnail! Full version at https://castalia.dreamwidth.org/file/3340.png (minus the 100x100 in the URL). :)

Also: nice icon.

Ah, that explains it. I was in a hurry and used the first code I saw when I uploaded.

And thanks, it's awesome that it's super relevant again!

ISN'T IT JUST. I have been massively enjoying the resurgence of fannishness, and thinking slightly wistfully of the heyday of go_exchange.

Yes! Damn, that brings back memories. I'm glad so much of the older fic is available on the AO3 now.

Not sure if this is intentional? When editing a comment, I am accustomed to being able to type the edit, tab to the Reason box, and hit Enter, and that posts the edit. (I know I should tab again to the Update Reply button, and it does work if I do that.) Now it brings up the icon browsey thing. I don't know how it's doing that when my cursor blinking in the Reason box tells me the icon browsey thing isn't the thing the Tab key selected for me. Waterfox in Windows.

Edited 2019-06-23 18:28 (UTC)

Oooh, thanks for this -- flagging it up to the dev who's working on this manner of thing!

I wonder if it's related to the issue

snickfic is having a little upthread? Different typy box, but that might not matter?

I don't think that's intentional. At least, I'd rather not bring up the browse box when you press enter in the edit-reason field!

Edited (test234) 2019-06-23 18:42 (UTC)

Hey! My reply box has started force-centering. I don't think it was doing that last night, so I imagine something since has caused it? Before, when replying to someone, my comment box when replying would slightly align under the comment I was replying to. Now, no matter if I am replying straight to the post or to a comment it is always dead center of my screen.

Not unusable, just a bit visually disconcerting because it makes me uncertain I am indeed replying to the right thing!

Win10/Chrome Version 75.0.3770.100 -- I disabled all my extensions to see if it made a difference and it didn't!

Yep, my comment box is also dead center in the middle of the screen. I also disabled my extensions (including dwtools) to see if that changed anything and it didn't.

I thiiiiiiiiiiiiiiink we just pushed a fix for this. Check it out?

Yep! Much better. Thanks!

Also, here.

The fix we just pushed should correct this! Sorry about the trouble.

Yes, it did! Thank you so much!

This is what I am getting when replying to a comment or entry. It's not a great look, to be honest... and that's putting it lightly.

I'm on Chrome (also using DW Tools). Big yikes.

Edited 2019-06-23 18:50 (UTC)

You're using DW Tools, which breaks things.

Please disable the Dreamwidth Tools extension! The author will have to update it for how the comment form HTML has changed.

67.0.2 (64-bit), Windows 10, Theme: Dark Violets by Musyc.

Thanks for all that you do, and good luck!

Hey there, can you take a screenshot to show me what you mean? Your theme looks normal to me, but I may be looking at the wrong spot.

The scroll bar appears to be back now, thank you! When I reported the bug, it was black on black on the right side of the screen. It's gone back to being light grey with a darker grey indicator of where I am on any given page.

Thank you!

You know what, I'll take it. Let us know if it goes weird again.

Will do. Thank you!

Could random and browse buttons be reversed? I find myself clicking random instead of browse. Not sure if it's just me now bc I think I'm supposed to click the icon still, hover - move right, hit random, sigh and then hit browse.

Alternatively if anyone knows how to kill the random button for me w/ a script too, will be happy with that as well.

I also find myself clicking random instead of browse. "Browse" is the button I use far more often (I hardly ever use random), so switching the placement of these two would be appreciated.

I'm getting some weird button overlaps on mobile Firefox (screenshot; Android 9, Firefox 67.0.3).

Actually, looks like desktop Firefox (67.0.4) too, now that I'm resizing my window. Not sure if a layout thing or a backend thing, but I'm also getting it on Chrome.

Also, I know you're still changing things, but I hope the random icon button isn't gone on mobile! That's what I use 99% of the time.

Hi! Sorry if this has been mentioned, but I found this problem last night and went to try and see if it had been fixed overnight.

I'm still replying to a post that has hit captcha. I've found that since the code push, this signs me out of my account. At the top I'm used to seeing myself logged in and I've never had to sign in via the comment before. I'm in the account that I want to post the comment in, but it seems to log me out.

I already see that someone's mentioned the icon going back to default, too. I had that happen 8-9 hours ago as well and it's still happening.

I'm ngl, the new quick reply comment layout is really confusing as it stands this morning. I know I'm a creature of habit and that all things take time, and that the DW team owes us really nothing when it comes to the DW tools extension, but I'm not sure if there's anything that can be done to align everything as boxes instead of long rectangles.

I really like the icon on the left hand side as I always have to press "preview" to see which one I've picked. Thanks for all your hard work and for being so patient.

Thanks for having flagged this up!

roadrunnertwice found the cause and wrote a fix, which I think is now live on the site -- can you let me know if you're still having problems?

Thank you so much! It now works like it did before and doesn't log me out.

roadrunnertwice, thank you!!

Brilliant! Thanks for letting us know :)

yay, glad it worked! 🙌🏼

edit: Also, about the formatting on the dw-tools extension: once things settle down and we have an adjusted quickreply design that can hold steady for a couple months, the extension developer should be able to make things look good again. (Actually, fixing it should be way easier than getting it right the first time was. TBH I have no idea how they were splicing stuff into that massive table.)

Edited 2019-06-24 20:54 (UTC)

Thank you so much for taking a look at it and fixing it so quickly!

I completely understand — except I don't when it comes to coding, lol. I know it's not Dreamwidth's problem, especially since it's not a tool created by the official Dreamwidht team, and I don't expect Dreamwidth to fix something that isn't really their tool anyway. Hopefully the developer can update it — and if not, I have my keyboard shortcuts to fall back on if I dislike the look with the extension turned on so much.

Again, thanks so much for fixing the problem and taking the time to reply!

I still really miss having the journal name present with the comment box instead of just icons; when switching between accounts, this is still going to create an immense amount of confusion.

Might not be a concern, b/c it's not an actual bug, but I do really wish that was still there. Could that be accomplished by condensing icon options to their own line? (Maybe making the buttons the same size as everything else, putting the buttons and drop down on a single line, and using the space to keep the account name/linking intact?)

Edited (I clearly know how to close parentheses.) 2019-06-23 21:55 (UTC)

Hmm. That wasn't on my radar for this redesign.

In the future I'm hoping to improve the "switch user" controls in the really big comment form and make them available in the other forms, which would make that a lot nicer. In the short term, IDK. It'll depend on whether more people ask for a user tag.

This comment got buried somewhere on page 2. I also would like to see it again. It's a good reminder (other than the icon) to let us know which journal we're using, for those of us who switch between multiple journals. Thank you for keeping it in mind!

Yeah for people with multiple journals it helps a lot to see which one I'm logged into because I don't always remember when I switch tab after tab, etc.

I vary my screens and can't always easily get to my username at the top of the page, etc
I'd very much like to see my username header at the top of the comments

rpers get a lot of use out of referencing specific pages in our journals and shortcuts are really, really helpful

it'd be nice to have, and i think the more people notice it, the more people will wish it was back. the absence is a low level annoyance similar to how now when you log out, you're taken to a screen with the top right meta inexplicably missing your username.

Yeah, this is one it probably is worth adding back in; apologies for not having thought of it/remembered to bring it up in discussion!

[... oh gosh it's going to take me a little while to get used to the Post Comment button apparently being in a different place. This is not a complaint! I'm just laughing at myself.]

Yeah, I've been thinking about this too. Maybe the username and "More Options" could go on the top line, icon dropdown and Random/Browse buttons on the second line, and subject on its own line below those? That seems like it would be good workflow.

Quote would be a bit of a sore thumb, hm. Probably should go somewhere above the text-entry box, maybe wherever other buttons, like from the DW Tools extension, go? Because it got mentioned in this post, I just downloaded it and it's kinda cool: I can create my own buttons for HTML, even if they currently look all stretched out!

Quote's the odd-one-out right now for sure. "More options" is really a partial "submit" button, so I do think it belongs down below with post and preview.

This is all "redesign the talkform" territory, though — I feel like everyone agrees that we need formatting buttons and a markdown/HTML mode switcher, and trying to get the current controls lined up ~just right~ ends up being wasted effort past a certain point because we'll have to shift everything around shortly anyway.

Mm, I can see how from a backend perspective it looks like a partial submit...but I think the main reason for people to use it is going to be to swap accounts, and I think if you put the username up there and people see that it's not the account they want to post from, they're going to be looking around there for a option to switch.

(What other Options is it for? Subjecticons, the autoformatting ticky, and the link to the icon page all seem pretty niche comparitively.)

On further consideration, I think letting the Quote button hang out at the right end of the Subject line might be ideal (at least until there are more formatting buttons for it to hang out with) because that's the point in the workflow (deciding what the post is about/replying to) that it naturally would go.

I admit I didn't ever use Quote or even know what it did before today, ha, because it looked like part of the auto-format option so even if I wanted to quote and reply to something, I'd just do it by hand!

I really appreciate all the thought you are putting into interface options. Just saying.

<3<3<3

Please. It would be very helpful to have it back.

Less of a huge issue but other people don't seem to be having the same problem - my icon name box is HUGE and way overshadows the subject line box, which is really frustrating. I understand if this is just the way life is now, but I have friends who have been sharing screencaps and their icon name box is much smaller and in line with the "random" and "browse" buttons, instead of below it like mine.

(I know I currently have DW tools turned on, but I turned it off and it didn't change anything, other than to remove the giant "text tag" and "action tag" buttons. The icon name box is still just as huge and under the random/browse buttons.)

I'm using Chrome Version 75.0.3770.100 (Official Build) (64-bit) on a Mac. I've tried refreshing, clearing the cache, and commenting on a bunch of different pages, no dice.

Definitely not a huge issue for me either, but figured I'd share since this happening to me as well since this afternoon. Doesn't seem to matter if I disable DW tools--my icon dropdown menu is much larger than the subject line and stays that way. The font also went back to a smaller size (the same size it was prior to the push).

How it looked this morning. How it looks now.

I use Chrome and Vivaldi on a MacBook.
Chrome: Version 75.0.3770.100 (Official Build) (64-bit)
Vivaldi: 2.6.1566.40 (Stable channel) (64-bit)

Seen this on two polls now, Google Chrome on Windows 10 (theoretically with all updates): the middle of the poll bar doesn't show, only the red on either end with the count after that. I haven't tested it on mobile but I imagine it would be entirely broken there; those tend to compress to one line length on Safari on iPod Touch.

Edit: confirmed, the polls are also broken on Safari (only the lowest number of responses present in a given poll has a distinct line length, the others go all the way across with a red dot at either end) and the numbers are partially offscreen. Not an accessibility issue for me, but potentially for others.

Edited 2019-06-23 22:39 (UTC)

Thank you for letting us know! I've flagged this up to the dev team.

I posted in another comment thread about this, but I'm not sure if you'd spot my comment there (it was buried pretty deep), so I thought I'd provide a screencap of the interesting new comment box I have, which is much more minor of an issue than some here, so I understand if it doesn't get tweaked or anything!

Now when I reply on a post, I get this, which looks a little odd with regards to the stuff above the actual comment box:

I'm using Firefox on Linux - and no extensions or hacks that should affect the way DW displays.

Perhaps this was intentional, in which case I will have to learn to live with it. If not, however, these are my thoughts:

I'd rather the subject line be where the icon-choosing dropdown is, and the icon-choosing dropdown go next to the Random button, because honestly, I don't have any icons that need the full length of this box to see their names, and I don't need the extra few character spaces of subject lines (which I rarely use anyway). (Also, the subject line is the same font size as here, which is not really an issue, only me being nitpicky - I just would've thought it would be a tiny bit larger.) But if there's a good reason for this to be this way, let me know and I'll understand. :)

Thanks for flagging this up! Mark is pretty sure he knows what's broken; he's out and about without a keyboard at the moment, but is aiming to fix this by the end of the evening, Pacific time. Apologies for the inconvenience!

It's intentional! (The only wonky part of that shot is the tall dropdown and tall "Random" button — we adjusted those sometime after you took the picture.)

What's driving this design is that the comment form HAS to be usable on mobile. During development, I tried collapsing the dropdown, buttons, and subject into two lines beside the icon, like you're describing. It didn't work very well — the icon dropdown and subject line were just illegible once you hit like two comments deep on an iPhone SE. That's fine if you don't use subjects, but a bunch of people do.

(You can open up some extra space by using symbols instead of words for the buttons, but that had some interesting engineering complexities and accessibility concerns; we're still looking at that, but it's not ready yet.)

(Why not collapse it when it's wide and then let stuff wrap down below the icon when it's too narrow? Well, we might still do that, but 1. it's tricky to get it resilient enough that it looks okay at every width, and 2. we don't want it to feel like the controls are in a different place every time you look, because that's even more annoying than it sounds. Worst case scenario would be "sometimes the dropdown is flush with the icon, and sometimes it's off to the right somewhere with one or more buttons in between.")

Flat | Top-Level Comments Only

Page 3 of 5

Code push has happened!

Known Issues - Fixed 'em Maybe?

Known Issues - Pending

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

no subject

no subject

no subject

Delays on importing from LiveJournal?

Re: Delays on importing from LiveJournal?

Re: Delays on importing from LiveJournal?

Re: Delays on importing from LiveJournal?

Re: Delays on importing from LiveJournal?

Re: Delays on importing from LiveJournal?

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

+1

Re: +1

Re: +1

Re: +1

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

Re: user tag not displaying correcting for AO3

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject