The "Updated Miscellany" beta

[roadrunnertwice]

Hello! As of late April 2020, there are two new beta features available on dreamwidth.org. You can turn them on at the usual place.

• The first one is Two-Factor Authentication. 2fa is an optional thing where you log in with your normal password, but then have to confirm the login with an app or security key before you can actually get in. You might have used it for your email or for important work accounts; soon you'll have the option of using it on Dreamwidth.

  Important note: currently, we only implement the setup phase. You can configure a 2fa device, but DW won't yet actually use it to enforce access to your account.

  The rest of this post isn't about the 2fa beta, because I don't know as much about it! There will probably be a more detailed post about it later, once we start implementing real login protection with it.

• The second one is called Updated journal page components, because it's extremely miscellaneous and I needed to call it something. That's the one this post is about.

  tl;dr: better comment pages on your telephone. Especially if you use Android and it usually looks like a bomb went off in the reply form.

What's in the Beta

This beta messes with the following Stuff:

• Site-skinned comment pages.
  • They 🌻 work on mobile 🌻 now.
  • Should look mostly the same, with very minor differences.
• The "more options" reply form.
  • Similar functionality as before, but it now resembles the quick-reply.
• The icon browser (for paid users).
  • It's new and improved. This is an update to the rewritten icon browser that was previously available on the beta new entry page.
  • Does the same stuff as the previous icon browser, but works better on mobile and makes better use of available screen space.
• Icons pages. (https://<USER>.dreamwidth.org/icons)
  • Same thing as comment pages: better on mobile, mostly unchanged.

(You can see why the name of the beta was tricky. These things don't SEEM like they should be related at all, but due to Reasons, they are.)

Known Issues or Non-issues

Stuff we're already working to fix:

• (Fix pending) Minor display glitch in Tropo Purple's header at mobile widths.
• (Fix pending) Page-switching links on multi-page entries or icons lists got smushed together a bit.

Stuff that's intentional, so we're not working to fix it:

• On Tropo skins (red and purple), the comment page font size (13.6px) is a little bigger than it used to be (12px).
  • It's still smaller than the widely-agreed best practice on the web (16px), but it'll be a noticeable change for DW users. We hope you can get used to it in time!
• In "more options," the spellcheck checkbox is gone.
  • That spellchecker is outclassed by the built-in spellcheck in most web browsers, so we're gradually sunsetting it.

Stuff we already fixed:

• Extra "Thread" link in each comment's footer.
• The "in-between" reply page you land on if you need to fix a mistake or do a captcha is now in the beta. (https://www.dreamwidth.org/talkpost_do)
• The comment preview page is now in the beta.
• In the "Drifting" journal styles, the "more options" form got pushed down past the end of the sidebar content.
• style=light (and the Lynx site skin) was Wrong with the beta enabled — too many non-browser-default colors and fonts.
• New icon browser cruelly sent your keyboard tab position to Oz when you were done using it, and couldn't really be navigated with the keyboard anyway.
• On Gradation skins, the comment page font size was smaller than it should be.
• The nav/action box on entries could sometimes get too close to large mood theme icons.
• Code blocks (like <pre><code>...</code></pre> as opposed to plain <code> spans) looked bad.
• The username indicator above quick-reply looked weirdly small.
• On site skin pages, you couldn't resize the reply form to be wider than its starting width.

How to Help

Turn on the beta, use it for a while, and let us know what's not ready yet!

• Please read the "known issues" section above before reporting problems.
• Please include your operating system version and your web browser version when reporting something!

What we most want to know is:

• Is anything unusable or broken in your browser, especially in the site-skin comment pages?
• Does the new icon browser break? When and how? What sucks about it?
• Does the rearranged "more options" reply form break? When and how? What sucks about it?
  • (Please try living with this one for a day or three before declaring it wholly bad. I know moving controls around in the reply form is inherently traumatic, but we're trying to get this right for the long term on both mobile and desktop. Thank you for your patience AND for your feedback.)

Many thanks to the users who have already reported issues! 💖

Comments

[cesy]

Found an oddity: https://www.flickr.com/photos/97098138@N08/49867817542/in/dateposted-public/

On the top nav, my username seems to have wrapped onto a new row on top of the logo? Chrome on Android.

[roadrunnertwice]

You mean where it says "cesy" on the left and "Menu" on the right? That's by design; it predates this, but you might not have noticed it before since fewer pages used the updated site skins. If you tap the name, it brings up a menu of the stuff that goes in the upper right corner at desktop sizes.

But thank you for drawing my attention there, because!! it looks like Tropo Purple has a display glitch behind the username that doesn't affect any of the other site skins.

[stealthsystem]

Do you happen to need mobile accessibility testers for this stuff? Most of the time, my mobile doesn't look like a bomb went off because screen reader use, but if you still think it'd be useful info even if I can't see any of the visual components, I'm more than happy to turn on the beta and find out, since I'd meant to anyhow.
-Luke

[roadrunnertwice]

Sure thing, thanks! (With the caveat that the icon browser is a little busted at the moment, per above.) The hope is to turn this on for everyone eventually, so might as well give it a test run now.

My hope is that you won't really notice much difference, tbh; the size of the touch targets might be a little more consistent, but that'd be about it. All the semantic markup is unchanged.

[madfilkentist]

When I create a post with JavaScript turned off, there's no way to set the time. This results in a time zone error that makes my posts appear to be posted several hours later than they were.

Dreamwidth has an excellent record of supporting most functions with JavaScript turned off (the big exception being uploading images), and I hope it will stay that way.

[roadrunnertwice]

Beta create entries page? Or classic?

edit: Tried it on the beta page with no JS -- looks like there's a nasty bug where clicking the "picker" buttons just submits your post instantly, so I'll get on that.

But I tried typing in a date and time (in a format that matches the format of the default values it gave me), and that worked just fine.

[jeeps]

I know you're not working to fix the larger font on the Tropo skins, but I still think it bears mentioning that I turn mobile beta testing on and off every time I switch between mobile and desktop because the huge font on desktop is such an eyesore.

[roadrunnertwice]

Yeah, I know... 12px is really untenable as a default for the modern web, buuuuut people like what they like. :/

Ideally, I want some customization for the site skins; I'd rather that we have only one "main" skin (leaving aside the oddball tall-side-nav skins) and let the people choose their:

- Main background color
- Main accent color
- Desktop body font size
- Mobile body font size

...but there are some technical limitations that would need to be overcome first.

In the meantime, you can use a "user CSS" browser extension on desktop to bump that font size down. With the current state of the beta, you ought to be able to just do something like

#page .entry, #page #comments, #page .reply-page-wrapper {
  font-size: 12px;
}

...and target it at all of dreamwidth's subdomains.

[thepnutgallery]

Hey all,
not sure if this is one of the beta things or what, but when I go back to Edit my entries, I can't seem to find where to edit the date anymore. Thanks for any help!

Eric

[roadrunnertwice]

Did you turn on the create entries beta too? If so, you need to configure which panels are shown. See previous comment.

[falkner]

Something minor about the new Create Entries page that's in beta: it still has the "Spell check" button despite it having been removed from comments at this point.

[roadrunnertwice]

Yup yup.

So far, we’ve only been removing spellcheck when it’s getting in the way of something, and that instance hasn’t gotten in my way yet. I’m sure it will eventually tho.

[spaghettimonster]

One thing I've noticed: I don't see an option for disabling auto formatting in beta. I wouldn't want to write out a complicated html page on mobile, but I do sometimes like to do small revisions (adding a line or two). Doing so with beta seems to default to auto formatting, regardless of the page's previous setting, which can end in things getting spread out badly (so many br spacings).

[roadrunnertwice]

Checkbox is still there in the more options comment form, so you must be talking about the create entries beta instead of the updated misc beta.

Yeah, the new entry form doesn’t have that right now. I’ve been working on evolving that whole feature, and my work just got merged. So next code push, there’ll be a dropdown for choosing your text format, in entries and comments both.

In the meantime, use the <raw-code> tag to disable autoformatting in part of a post. If you're stuck on mobile and need to edit a "no-autoformat" entry, I guess the thing to do is just put the raw-code tag on either end of the whole entry.

[gardenerofavalon]

Really odd random bug: in the new update, ALL username links turned to to the "visited" link color for me. Other links were unaffected and displayed normally.

An example of what it looks like with the latest update here

How it looks when I turn on the beta for reverting it to the older version here

As you can see, the link for a comment I've clicked on to view vs all the others is correctly colored in both, but while the old version only has one username showing up as visited, in the new one they're both the same color.

It's obviously not a HUGE site-breaking issue, but it's an oddity and a little confusing, especially when I'm scrolling through a very large post looking for comments by specific people. I'm using Tropo Red on Waterfox, no idea if it shows up in other skins/browsers, it's getting late and I'm too tired to test it right now.

[anemoneae]

I'm having this issue too, even on Gradation (Horizontal) and in an Incognito window on Chrome so it's definitely a bug

Color changes on Comments in Celerity Site Skin

[archangelbeth]

(Reposting my (screened) comment from the other post:)

Normally, I have a sort of beige-yellow sidebar, with darker or lighter beige-yellow for the "comment headers" -- this is Celerity Site Skin, I believe? (https://www.dreamwidth.org/manage/settings/?cat=display)

The changes make the Commenter headers (where the icon, username, and date posted are) gray and darker gray. It's... kind of clashy with the sidebar, and it's harder to read the Yellow-beige user-names on the dark-gray header. (And moderately upsetting in the "You have moved my cheese" way. If there is a programming reason for the color of the cheese to have changed from beige-yellow to gray, then okay, but if you can make the cheese match the Celerity Site Skin colors again, I would be very happy.)

Apologies if there are already a bunch of "AUGH, MY CHEESE IS THE WRONG COLOR" comments. I wish there was a way to Search This Entry's Comments that was, I dunno, near the number of comments or something. O;>

[laconism]

the new update has broken the formatting for a character stats code that i use for this roleplaying journal. for some reason, the tables have an alternating white and gray background when they're supposed to be transparent (defining a background color only changes the white part) and the borders and margins are all messed up too. however, when i view the entry in preview mode everything looks the way it's supposed to.

here is an example of how it's supposed to look and here is how it looks in the new update. the journal entry itself is here and the full code is here if that helps at all too. i use google chrome and the issue persists on my iphone as well.

i've temporarily reverted the updated components to fix the issue for now, but thought i'd drop this here in case there's any way this can be fixed within the confines of the new update.

New codepush pages

[random_xtras]

Hi, the new site skin pages, with the bigger, darker writing, gives me eyestrain. I have turned them off, but Jen said to let you know about this. I use DW a lot, and have one paid account and several free ones, one of which I use daily. I also read on DW a lot because I like to read my own bad fanfiction. Could there be some way to make the pages look the old way, even after the beta testing's over? Please?

[teal]

Question, not sure if this is the place for it, but since this is the first place I've seen it mentioned. (And I'm here mostly from the recent maintenance post, alas.)

What was the prompt for two-factor authentication??? It doesn't really make sense for the website's general use. And if implemented, would this be something you'll be making all users do or will it be optional like it is for most sites?

[denise]

Yes, it will be an optional feature that people whose accounts are at higher risk (security researchers, activists, victims of domestic abuse, journalists, etc etc) can enable to protect their account if they want. It's part of our ongoing project of security upgrades. We are extremely aware that many people hate 2FA and start to worry whenever a website mentions it, but there are multiple use cases of the site where someone's account is at higher risk, and those people have been asking us for 2FA for a while.

Right now the only part that's been implemented has been adding your 2FA auth method, and it doesn't actually fire on login, but with 2FA the hardest part is getting the 2FA method added to your account, so we started there for people to find the first set problems.

[amorality]

The new layout causes me quite a bit of eye strain, so I have turned it back to the old one. It makes reading on old devices (I have an old laptop) very difficult. I have rolled the update back for now, but I would appreciate if you allowed "classic" mode to remain for the foreseeable future. In addition to all its other problems, one of the things that caused roleplayers to migrate en masse was the updates that LJ refused to rollback that gave users migraines. I have chronic migraines, and seeing these concerns be screened and essentially dismissed is incredibly disheartening.

Please listen to your users. It costs nothing but a bruised ego to allow us to decide on our own if we want to keep these changes or not. If I might make a suggestion, I think handling it like reddit did would be nice. They listened to their users and implemented old.reddit.com to allow people to CHOOSE how to browse their site.

[alexseanchai]

The problem as I understand it is that the cost of keeping the old version is the ability to add a bunch of features that people have been asking for for years.

The secondary problems as I understand them are, one, the set of "people whom these changes hurt" and the set of "people who helped beta-test these changes" did not overlap. (One of the less vicious of the angry comments on the dw_maintenance post demands to know why the changes weren't beta-tested first; I've been beta-testing them since May.) It is difficult to listen to any particular subset of Dreamwidth users—for example, people who get eyestrain or headaches or other such issues from the just-implemented changes—if none of them say anything. Relatedly, if you are able to identify specific ways the format could be changed to reduce your eyestrain and avoid setting off or worsening your migraines, the Dreamwidth coders and the coders of custom site styles would love to hear from you.

And two, when a hundred people descend on the Dreamwidth coders in full vengeful Furies mode, complete with talons, both current and potential future Dreamwidth coders get discouraged. As you would do and may have done upon a hundred furious messages about major problems with something you worked hard on for years, that you thought you'd fixed all the problems with because you'd fixed all the problems you found yourself or were told about. If the intent is for Dreamwidth to do better in future, instead of for Dreamwidth to do nothing in future, it is counterproductive both for users to do this and for coders to listen.

Seriously, if you have thoughts on how to alter the new version to keep it from hurting you, please share.

[trueaussiedoc]

I've just turned on the beta testing for the journal page components and it told us to jump over here to report any bugs as to the reason for reverting. I apologise in advance is this sounds stupid (it will) because I have no technical skill whatsoever beyond simple user-friendliness, which is one of the reasons why I use Dreamwidth. I've been using DW for years now, having come over from LJ when they pulled all their crap years back. When I came over, I was recommended a user-developed site skin to allow the pages to have similar colouring and spacing as the old LJ (screenshots here), as it was extremely beneficial to me, someone with chronic illness and sensory processing issues. The white and blue with the text spread across the page just seemed easier to utilise without stirring up sensory issues for me. I've been using it without issue since 2012.

The latest code push seems to have removed the Stylish extension's ability to convert the comments pages to this adjusted layout and was sticking with the light grey/purple and the comments condensed to the middle of the page with large amounts of 'white' space padding of the default style and it was difficult for me visually. My problem is, I have no idea what "bug" to report here or what part of the extension's CSS code was affected to prevent it working. There were no problems when I switched on the beta testing.

I understand changes are inevitable with technological advancements but would really appreciate an option that allows extensions adapting layouts for usability for people like me with medical issues to still be able to use the tools that help their frequent use of DW continue without problems. It's impossible to address everyone's needs but I know those of us with medical visual issues would much appreciate if their usuability could be taken into account when any permanent changes to layout are considered. I didn't realise beta testing for this came out in May but I have now tracked this comm to be alerted of any upcoming changes.

PS. If anyone has any idea what part of this extension's code would've been affected and knows a work-around to keep the site skin adaptations working on the beta version, I'd much appreciate the help!

[denise]

Unfortunately, it's not technically possible for us to prevent third-party skins, extensions, and userscript layouts from breaking occasionally -- like, not "it's something we could do with enough effort but we don't have the capacity to make the effort", literally "computers don't work like that". (It's because we don't control the skins/extensions/add-ons/userscripts/layouts/etc, and therefore any change that we make to the site for any reason has the risk of breaking them, depending on things like how the author created them, how much they thought to future-proof them, and whether they're targeting specific code blocks that we've had to change.) If you know who made the skin, you can point them at dw_dev so that they can be aware of upcoming changes and adjust the CSS of the skin accordingly, and if they're ever stuck on what needs to change, they can ask us.

In this case, I suspect that the problems you're having will improve when we fix the other issues with spacing and padding that were covered in last night's dw_maintenance post, though, because at a quick glance it looks like that skin is primarily just changing the colors.

[baffi]

I came here from Live Journal and one of the reasons I stayed and bought a paid account was the option to make LJ's Flexible Squares template work. So far I never had any issues, but the new comments form is completely broken in my journal. The icon preview doesn't change when I pick another icon. The randomiser as well as the icon browser are completely gone. Parts of the form that should be invisible until you choose 'OpenID' or 'Other Dreamwidth account' are permanently visible.
Here is an unlocked entry for you to check: https://darciana.dreamwidth.org/133677.html?mode=reply

It's till manageable though it looks awful and has limited functionality, but I'm afraid other changes that might come will make DW unusable for me. Changing my layout is not an option. Complicated reasons. :(


The new default layout pages are a big problem as well, literally. Everything is huge, the font is monstrous compared to most other sites I visit. Perhaps it looks okay on mobile. That isn't relevant for me, and it would be pretty off-putting if desktop users are deemed irrelevant (again). I remember that from LJ. It would be another reason for me to leave. Or give your users at least an option to change the font size, like Twitter does.


I'm glad this place exists, but right now I'm pretty anxious that this last possible home for my journal, as inactive as I might seem, will go the way of the dodo for me, just like its predecessors.

[roadrunnertwice]

Hey -- sorry about this, but it's an unintentional bug introduced in one of the last couple code pushes. It's fixed in the code, but the fix hasn't gone live yet -- that'll hopefully happen soon. While you're waiting, you can go to the beta features page and disable the updated components; that should fix the comment form and things like cut tags.

Once the fix does go live, you're going to need to edit your custom style in order to take advantage of the fix. It's a one-line change, though.

The latest code tour has a brief description of the problem and the edit you'll eventually need to do (cmd-F for "2819"), and there'll be a post in the style_system comm with more details once the fix goes live.

As for the site-styled pages, there's some changes coming that we hope will make things feel better. For what it's worth (caveat: I don't speak for the site owners, so this is just the perspective of a person who's been contributing some of this code):

• We're not deeming desktop users irrelevant.
• All of the chaos right now is all about putting the site in a better position for the next ten years.
• All of the chaos right now is a prerequisite for making improvements like allowing people to configure their font size or colors on site-styled pages.

Thanks for your patience, and sorry for the inconvenience.

[lylith_st]

Hello! I've been trying to use the new create entries page for a few days now and I was wondering if you got rid of the rich text option entirely or I am just not seeing it?

It was a very quick and practical way to write entries because it made it much easy to change font size, color, add links videos, etc...than having to type everything down in HTML (or Markdown or Raw). Some users like me just don't have memorized all the shortcuts and this sort of change makes it harder to use the site.

I'm also still having issue with the bigger font causing some eye strain but I'm mostly a desktop user too. I know you guys are trying really hard to make the site work for everyone, I don't want to sound like I'm not taking into account your hard work or the fact you're dealing with a very outdated site that needs to have its very base code rewritten, but it does feel a little like with the overall new changes, desktop users are often getting the short end of the stick.

[roadrunnertwice]

Beta create entries doesn’t have rich text mode yet, which is pretty much the reason it’s still “beta.”

Thx for the feedback on the reading experience; I’m hoping some upcoming changes will make it feel better. We plan to keep adjusting to make things as good as possible on both desktop and mobile.

If it seems like mobile got priority in the last pass, it sort of did, but not because we think it’s more important; it’s because it’s harder to get mobile into an acceptable state, and you can’t start with “good on desktop” and work backwards to “ok on mobile;” if you don’t want to drive yourself nuts, it has to go the other way around.

[razorblade_empress]

I'm not sure if this is the correct place for this, and I think someone might have reported it already when the beta first went live? but I use the Gradation Vertical site skin on one of my rp accounts, and as with the Celerity skin, the new beta squishes everything over to the left so half the page is empty space. The type also appears to be smaller now that I've compared it to the same page with the beta turned off. I'm on desktop, using Vivaldi 3.2.1967.47. [Beta on | Beta off]

[roadrunnertwice]

That appears to be sort of by design,* but I'm interested in hearing more about what people want the vertical nav skins to act like.

The vertical nav creates a strong anchor to the left side of viewport, and that has implications for the whole rest of the page. There's a few ways that can shake out:

|n ccccccccccccc|

— No max content width, whole page fills the WHOLE viewport. That's what the old gradation-vertical did, but it's generally considered hostile to people with reading or vision disorders, so the policy is to try and not do that.

|n ccccc        |

— Limit content width, anchor content and sidebar to the left. That's what the new gradation-vertical does. Results in a wonky empty space to the right, sigh.

|n     ccccc    |

— Limit content width, anchor sidebar to left but center the content. That looks more balanced, but it's less usable because the nav is half a mile away from the content.

|    n ccccc    |

— Limit content width, center the nav and content together. Looks more balanced, but it's less usable because the nav isn't on the left anymore, it's in the leftish-off-center.

IDK. Which one would you expect? (Personally I hate them all, which is why I don't use gradation-vertical.)

---

* This is one of those choices that predates the updated comment pages by years, but hasn't been widely noticed because the really important pages weren't using the new site skins yet.

Create Entries

[bloodbathing]

Hello! I turned on beta testing for the new Create Entires page and decided to poke around at it. I noticed that if I try to post two entries with the same content (e.g., "test"), only one of those entries appears. The other seems lost to the ether.

On another journal, I tried the same thing without turning on beta testing. It, too, only creates one entry. So maybe this isn't a bug with the beta testing, specifically? It was just something that made me go, "Huh!" So I figured I'd trot over here and report it just in case. :)

[apollymi]

I feel like I've seen this listed before as a known issue, but...

When I am looking at the beta Create Entry page on Google Chrome with my Mac, the tags section looks like this:


I do not see entries this way on Opera or Safari... or Windows Chrome.

I'm using Gradation Vertical, on an Apple running OSX 11.1 Big Sur. I'm on Chrome version 88, but it has existed previously.

[roadrunnertwice]

Can't reproduce this, but very curious about it.

Hey, are you comfortable with using your browser's "inspector" dev tools? Would you like to be? Since I can't reproduce the bug myself, I'm at the mercy of whatever I can learn from someone who IS seeing it.

On Mac Chrome, the shortcut to open those is cmd+option+i. If you open it while you're viewing the create entries page, you can spy on all kinds of shit. What I'm curious about first is:

• Look at the "elements" tab and find the top-level "<html>" element for that page -- it should have a bunch of classes on it, like honestly way too many classes.
  • Does it actually have a bunch of classes?
  • Are "fontface" and "generatedcontent" among those classes? Or are they missing?
• Look at the "console" tab -- are there any suspicious warnings or errors in there?

Alternately, if you can figure out anything else about when that bug happens or doesn't happen, I'd love to hear it.

[vriddy]

Apologies if this isn't the right beta post to reply on. I was going to open a support request, but poking around further I think maybe "Don't show on reading page" just isn't meant to work with Communities? I'm using the beta 'Create entries' page.

When editing an existing entry in a community and checking the "Don't show on Reading pages" box, the changes don't save and a "Can't make back-dated entries in non-personal journal" message is shown, even if there were no changes to the date, or updating the date to current time. This also happens when creating a new entry.

Unchecking the box allows the changes to be saved.

I wanted to hide a couple of FAQ-style posts in a new comm to avoid cluttering Reading pages, but it seems like this isn't an option which is fine - the error message is just confusing because I was also making other changes and didn't realise it was the checkbox that was the issue.

I found a similar problem in the support requests but opening a new tab didn't resolve it in this case. Using Firefox.

[anneapocalypse]

I'm seeing the same message under the same circumstances. Just backdating a Community entry works, but checking the "Don't show on Reading pages" box gives the "Can't make back-dated entries in non-personal journal" error message. I'm also using Firefox, on Windows 11.

null

[lemonsharks]

Do y'all have any additional beta updates since this post was made in 2020?

[feistro]

Sent in a support ticket about this, and they sent me here!

Long story short, I noticed icon pages are wonky. They look like this when logged in:

https://images.plurk.com/50NwU4JkKFQH9NZwAA0qdt.png

I looked through the past tickets to see other people have submitted this problem, and the stock answer seemed to be "turn on the 'Temporarily revert updated journal page components' feature." But when I do that, the site looks like this:

https://images.plurk.com/54tXwiM04qVu7RyxsAgh42.png

Which I get is supposed to be the default way the site looks now, but ever since it got updated with the newer code back in 2020ish, that has been a real hassle for a lot of folks, myself included, mostly because our eyes want to track to the edge of the browser, and all the empty white space makes that not happen. My native resolution is 1920x1080, so it's pretty wide normally.

Basically, can we get a default style or Tropo skin where the entry and comment boxes go all the way across the usable space rather than in just a little column in the middle?

Edit: it's the same problem described here.

[china_shop]

I turned Updated journal page components on yesterday, and I've just noped out and turned it off again. On a desktop (with entry pages always in Light Format), in Firefox, there's no margin anymore, so the text is way too wide for how I have my browser. :-(

Also, if I click the reply link in a comment notification email, I can select an icon but there's no icon preview. (That might be an actual bug?)

[roadrunnertwice]

Pardon the lag in replying, but: I think the version you noped back to is actually the new version of things, so... we're all good here.

(The setting for that is confusingly worded, because of a limitation in the way beta features are implemented. The default with the "revert" beta turned off is the new version of things, and the optional mode with "revert" beta turned on is the OLD version. The old version lacks margins in light mode, and doesn't support icon previews in the click-through comment form... all of which is part of why there's a new version.)