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

Did the Rich Text editor go away?

[mbarker]

Using either Chrome or Safari, I'm not seeing any Rich Text editor? I click on the tab, and nothing?

Re: Did the Rich Text editor go away?

[cesy]

(just a fellow user)

Not intended to be gone. A couple of other comments have said to try clearing cache and refreshing, and disabling extensions. If it still doesn't work, comment here again to confirm as we're collecting more data, e.g. which versions of Chrome and Safari and if it's Mac or Windows.

[falkner]

When I go to the post entry page, if I switch from HTML to Rich Text and then back to HTML, suddenly this code appears in the text area of the entry:

<script src="chrome-extension://hhojmcideegachlhfgfdhailpfhgknjm/web_accessible_resources/index.js" type="text/javascript"></script></pre>

(Using textarea because I don't know of a better way to post it unedited.)

[soupervillain]

The code that makes @username into username isn't working in some of my posts (e.g. the bottom of this one).

[roadrunnertwice]

Probably intentional!

I'm guessing that post has a <raw-code> block, because that's how to make artisan markup like your nav thingy not explode. Raw blocks now leave @ mentions alone.

We recently put a lot of effort into making @ mentions behave reliably, and making sure they DON'T trigger where they shouldn't. MOST NOTABLY, we no longer convert @ mentions in the following places:

- Entries/comments that are set to "don't autoformat".
- Inside <raw-code> / <lj-raw> blocks.
- Inside <code>, <pre>, or <textarea> elements.
- Anything imported from LJ et al.
- Anything from syndicated feed accounts.

We decided "raw" needed to be sort of an escape hatch that doesn't do any "auto" stuff to your markup, because there really needed to be SOME way to do that. So you can still link to users in there, but you'll need to use old-style <user name="yo"> tags.

[themightyflynn]

Hi! Cross posting seems to be broken? Don't know if it's just me, but trying to cross post to LJ doesn't work at all. When I went back to edit the entry to see what happened, the box to cross post was unchecked, so I checked it and posted and nothing happened.

[denise]

LJ blocked us again (we tend to trip their spam heuristics because of the volume "we" post at), should be fixed now

[kalloway]

Something is oddly broken on my masterpost for monthlysupergo.

It's showing everyone as struckthru for no reason!

When expanding nested cuts from the main monthlysupergo page, the strikethru seems to come and go.

(Win 10/Firefox, confirmed on Edge)

[momijizukamori]

Can you put the entry contents in a textarea here? I'm guessing this is related to some of the markdown changes, but I'd have to see the raw starting text to guess at how to debug it.

[chuckro]

My entries yesterday and today haven't crossposted to Livejournal. Any idea if the problem is on this end or theirs?

[denise]

LJ blocked us again (they tend to assume we're spam a few times a year because of the volume "we" post at, looks like the last whitelisting expired again) but it should be fixed now.

[taichara]

There seems to be a bit broken in the dropdown tab for icons, if there's an angle bracket in the icon name (this one worked for the longest time):



The icon still works, though -- it's the one I used here for this comment.

[roadrunnertwice]

Oh. Nasty. That looks like someone (me) thought it wasn't possible to have an angle bracket in the icon name.

[anthropophagite]

I can't seem to be able to use rich text. I'm using Chrome, but I tried Internet Explorer and it's exactly the same, even after clearing cache and cookies. I'm also on Windows 10 by the way.

[denise]

We'll look into this to see if we can figure out what's causing the problem, although please do be aware that the existing RTE is very, very old and broken in modern browsers and we can't guarantee we'll be able to fix it if the fix isn't immediately obvious. (We're working on a replacement for the new beta update page so we can get it out of beta, it's just not available yet!)

[assholic]

Glitch that I've seen happen more than once for me now is opening in a new tab incorrectly. I read rpa in flatview and a few times now I've tried to right-click open (parent) in a new tab to see the parent comment and it's opening the new tab as if I'm opening the rpa post without flatview from page 1. It's happened more than once and since last night, so I'm not sure if anyone else has had the issue or not. I'm on Chrome on Windows 10.

[denise]

Huh. That's incredibly weird -- none of the changes that we've made affected how threading is calculated, and the "parent comment" link is generated absolutely, not relatively (ie, it's not a case of your browser losing a referer header or referring information between windows). The only thing I can think of that might even remotely cause it are a few wacky edge cases... actually, I am pulling this theory out of my ass, but since you're an RP account, I'm gonna guess you use one of the cookie swap extensions like Login or Juggler, right? Try logging out of your account manually, delete the profile for that account in your cookie swap extension, create the profile in your cookie swap extension again, and then log in manually (not with the extension). Does that make it go away?

[maximite]

Not sure if this is a bug or a feature so to speak, but the new image zoom in/out function on journal entries seems to be clashing weirdly with images using flex display CSS - the images are displaying as tiny by default and only increasing to the flex container size when clicked. I'm guessing this is related to the Markdown move, but all the other image embeds I have on my journals seem to be working as normal, it's just ones with flex display in particular that seem to have gone wonky (playing around with the CSS elements under .entry-content img seems to indicate it's something to do with the max-width: 100% code, toggling that off returns it to normal but I'm not sure if I can actually override that within the nav code itself because all my minimal css knowledge is from google).

[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.

[theriomorphism]

Possible glitch. I edited out the usernames and content because it's not relevant and not mine to bring up, but I saw this when perusing a meme (trapped on a desert island: https://bakerstreet.dreamwidth.org/6377247.html) and considering I've seen a lot of glitches via images being reported, I thought I'd bring this up.



It LOOKS like the code for adding the image/icon to the comment above might have borked something with the code to put that huge gap before the legitimate icon in the post below. Since there was something with the code that's carrying over strikethroughs from deleted usernames to any usernames listed below, I thought this might be a carryover or related issue.

[cesy]

Does it happen to all icon images in comments, or just that particular one? Obviously it's not doing it for all images in general.

Do you know if the person who posted the image did any interesting CSS on it? It looks like the links that are normally below the comment have also gone to the side of the image.

(just a fellow user trying to help figure it out, since I can guess the kind of questions the devs will want to know)

[jeweledeyes]

I just have a question: When you said converting the profiles to markdown, I realized, are you going to be replacing the HTML formatting with markdown across the site? i.e. will I need to write my posts in markdown rather than using HTML formatting? I've been on the beta post mode for so many years, I just write all my posts in HTML. (I actually always switched into HTML mode, anyway, since I started on LJ wayyyy back in the day before they had rich text formatting, so that's just what I was used to.) I'm fine either way, just figured I would make a mental note of it if so.

[denise]

No, markdown falls through to HTML, that will always work.

[icon_uk]

Over on my board, people are posting images using ablode.de as a host. Nothing fancy, just the usual img src="image reference.jpg" style.

Regardless of their size, the images are appearing as the miniaturised versions on the page when it's posted, but when you click on them, it doesn't expand them, it takes the user directly to the image on ablode's site.

Any suggestions on how to fix this please?

[roadrunnertwice]

Can I have a link, if it’s a public comm?

If not, here’s the things to check:

- Images that are also inside a link tag (<a href=...) don’t get click to zoom, since that would break links. Sounds like these are all inside links.
- Images shrink to fit two things: the width of their container, and the height of the browser window. If the images are inside some other element whose width is constrained, they might shrink more than they would if alone. (That’s what you saw above: maximite had an image in a box that was configured to allow another box to steal space from it.) So if the image embed code people are pasting sticks the image in a table or something, that could shrink it.

On desktop, you can see what’s going on with the html by right clicking and choosing “inspect element.” That should help you figure out the problem.

Format=light color issue

[jesse_the_k]

Link color on format=light changed from deep blue to turquoise. On purpose? That same color is now a background on the post tools (previous/tags/memory/notification/next) above the entry box. The turquoise swallows the blue on the prev/next arrows -- I suggest you use a light gray to define the post tools?

Re: Format=light color issue

[roadrunnertwice]

Just to make sure, you’re using the “updated Stuff” beta, right?

- Obscured prev/next links: ah, yeah, that’s bad, thanks for pointing it out! We’ll fix it.

- Link color: only semi-on-purpose. There were already two different versions of each site skin, and for some reason the newer version of the “light” one used different colors. Now it’s more noticeable because comment pages use the new version.

[flangirl]

Is there possibly a code block you can give us to put in stylebot to get rid of the text (either "view all" or "browse") over the preview icon? I find it really hideous and distracting, and also feel it detracts from the whole point of having a preview icon in the first place - silly to call it a preview if I can't view the whole preview.

eta Obviously I hadn't actually used the picker yet, was still fussing with the code myself to try to get rid of the text. I do still find it ugly and jarring and it makes me feel like I have to pick an icon just to get rid of it.

[roadrunnertwice]

The button's default state HAS to have a label, because otherwise a bunch of people won't ever notice it exists.

But if you want to hide it for yourself, you can use:

#qrformdiv .qr-icon a::after, #qrformdiv .qr-icon button::after {
  display: none;
}

[jeeps]

I really miss the old icon browser button.

[jhumor]

I don't know if this is new to this code push or not, but when I use "my style" or "original style", in the header, there's a drop down list for filtering my reading page. When I select "site skin" (which I prefer so I can keep everything in way that uses less data), this option disappears.

Is this by design? Is there a way to add the filter reading page dropdown to the "site skin" option? (I don't see any ticky box to allow for this.)

[ilyena_sylph]

Just a user, but I have never located a way to put the navbar onto a site-skinned page either, and I have Certainly Looked because I like the site skins but miss my navbar.

[satismagic]

The rich text editor doesn't work for me anymore. Firefox 75.00 on Windows 10.

[denise]

We've been trying to identify the cause of this, but we can't reproduce it and none of the changes in this code push should have affected it at all, which makes troubleshooting almost impossible. Can you reboot your computer? If our current theory is correct, that may fix it.

[shanaqui]

Just to add in my feedback on the loss of the random button: this sucks. I might as well just get rid of my icons, and quit paid premium which I only have for icons anyway. I do not want to have to remember all my icons, or browse through them all; I just want to click a button, cycle through a couple until there's one that suits, and go.

And yes I know it's behind a click, but it was saving me time before, and now it takes extra time, and that is not fun at all.

I know this doesn't matter; everything breaks somebody's workflow, and I know it. But it breaks mine in a way that makes me angry, and I LITERALLY just paid for a whole chunk more of paid time I'm not sure I want anymore.

[shanaqui]

To add: I had actually found where random is in the dropdown icon list yesterday, and then today trying to leave a comment could not find it again. That's slightly more accessible than I thought when I was leaving the previous comment, but it's still not really gonna work for me. Particularly since I couldn't remember where it was having seen it literally yesterday.

[mycenae]

I noted this on the code push and beta, both the wrong place apparently, so I hope I'm in the right place, but the most recent code push messed with some CSS/div presentation on entries in a way I can't figure out how to fix.

The entry will still show correctly in the "preview" pop-up, but the post itself will not. No amount of "do not auto format" or < raw-code > fixes the problem, and I'm not sure what in the < div > or CSS coding I need to fix, because this was not a problem prior to the code push and this still shows correctly in Post Preview.

(I have seen other spacing/rendering issues in other codes, but I can only speak to mine/those I use and have direct access to). This is popping up on private posts, and I'm not willing to unlock them, but there is definitely something that changed in how entries present between before and after the push, and it still renders properly in preview but not the entry itself, and i'm just mindboggled.


I have tried this on multiple machines both WIN10, Android (mobile), and High Sierra OS. Resolutions differ, but my current default is 1920x1080. Browsers differ between Chrome, Opera, DuckDuckGo, and Edge. All present the same issue. I also use the default site presentation.

[denise]

Can you add the screenshots that you had in the dw_beta comment? The code and your CSS is most helpful, but if you can't share that, the screenshots may let someone figure it out.

[azurelunatic]

At some point, somewhere, I managed to select an icon, but the icon display did not update to the new pick. I'll try to pin down exactly what I did in case I notice it again. It was probably on mobile, which means mobile Chrome on the Pixel XL (OG).

[jhumor]

If you mean that when you select an image from the dropdown and the icon display doesn't change to the new selection, I noticed on my accounts with more than 100 icons, it sometimes takes a minute for it to show the new icon.


If you mean you've selected an icon, it shows the new icon and when you post, it reverts to the default icon, I have seen this problem on several browsers/devices:

On OSX 10.14.6:
TorBrowser (which sometimes has random issues anyway due to the browser's internal security settings).
Firefox
Safari

On iOS 12.4:
DuckDuckGo
Safari
Onion Browser

I have noticed it in all of these browsers. It seems entirely random. And it doesn't matter if I'm hard selecting the icon or if I'm using the new random option. Sometimes the icon posts correctly, but sometimes it posts as the default image, even if I've selected another icon.

Note: LTE is my only home internet (I hotspot to my computer, when needed), so I'm wondering if even though the entry page shows the icon as updated, if the connection speed has something to do with it not posting correctly.

[peaked]

Hiya! Question—I've noticed after the code push that my attempts to post gifs/images with a html code that has them as the same width isn't working anymore? (These gifs originally aren't the same size because I'm excellent at picking them!)

Usually I could do <*img src="IMG" width="250"> (or even use height) but now this doesn't seem to be registering. (Ftr, it registers when I preview the entry, but when I publish, it shows the gifs at their actual sizes and doesn't register my width command.)

Any help would be appreciated, especially for a html beginner!

Thanks for all your hard work btw.

[mycenae]

This has been breaking all over in my codes too (as seen above), ditto on the preview pane working and the entry itself being a big guessing game.

A quick fix that worked for me (at least last night) was to add styling to it to force it to work, (minus the spaces):

< img src="URL" style="width:250px;" >

It's not normally what I do when quick coding simple entries either, but it did get the page to respect the code.

[tessitura]

I've noticed some icons in some of my (and others') accounts being broken, and not loading, when the icon hasn't been deleted or renamed. Just there with the broken image picture and the icon's keywords. Clicking on the icon leads to a '403 forbidden' page. It doesn't seem to be consistent in deciding which icons to break, but it is super frustrating - especially for those of us who've paid for extra icon slots. Is there a way to fix this (without having to re-upload the broken icon)?

[roadrunnertwice]

No idea! Questions:

- Is it the same set of icons being consistently broken?
- Can you link me to a page where an icon is broken?

FAQ

[demoncutter]

hey hey, can we get "API" added to the FAQ? I did a search to find it and there were no results, I had to dig through the unofficial plurk to figure out where to go.

Re: FAQ

[roadrunnertwice]

That's a great idea. Everyone's a bit slammed right now, but I'll put it on one of the shared to-do lists, and hopefully someone can write something up soon.

[matrixmann]

I haven't really found a place where to post current bugs, but judging from the comments under this entry, this seems like a place this could be apprpriate...

Errr, first, it doesn't exactly have to do with the current code push, but something I deem important enough to have a look at.
Previously, I made a request in the Support Area (simply because I didn't know where to post it) on the problem which describes it as exactly as I can in the technical sense: https://www.dreamwidth.org/support/see_request?id=42052

I don't expect you can do much about it as it seems like the issue is caused by a recent code change on LJs side, but - well, maybe the tech people here can get a clue what has been changed and if there's a way that Dreamwidth can adapt to it (since the icon issue affects imported entries from LJ).

[denise]

Unfortunately, the importer is a very complex system with a lot of moving parts, and we don't have control over all of those parts because we're working with a data feed from elsewhere. This means there's a really limited number of people who can troubleshoot! I'm sorry about the hassle; if you leave the support request open, it will stay on the list of "stuff to troubleshoot when there's time", but I can't make any guarantees.