marahmarie: my initials (MM) (Default)

ETA: asked.

--ask around for s2 to move (back to) Top link from $this->print_body(); to $this->print_module_section("two"); - specifically, it should land right after .module-section-two but still within the same code block. More specifically, it should land after .module-section-two but before <div style="clear:both"> in the HTML above the footer (find screencap showing exactly where, if you post this).

This could fail spectacularly, but based on what I see in the live HTML editor, if I move the link where I say it should work and it actually works, it'll clear the page entirely on resized/mobile CSS (and on pages with very little content, which it currently can't clear even with CSS hacks) and stay where I put it - a 3-for-1 which, so far, has not been doable any other way.

marahmarie: my initials (MM) (Default)

The post title is in honor of my new default user icon. Like most images I create, it was done (re-done) in Paint.NET. If you reverse engineer it, it's still my old Dreamwidth icon, the one that says, "Sheep go to heaven and goats go to hell" with a lamb in the middle. You just can't tell anymore - thanks, Paint.NET! I've been meaning to work on that for a few years.

In other news, I've had recentish problems with others being unable to tell public from more private (say, access-only) posts, which I blame Dreamwidth for, at least in part. All there is to show a post is access-filtered is a single, tiny icon image (it's a gold lock, 16 x 16 by default, and while I'm pretty sure no one views my page in my style, I have it re-sized down to 12 x 12 in case anyone ever does; the original access filter icon image is here) which apparently isn't enough of a visual indicator to prevent a few "oops" moments others have had.

I hovered over the icon today to see if it at least has title text to tell you what it is or why it's there, but it doesn't. The alt text isn't informative, either; it just says "protected". Protected from what? Scratches? Bears? The public? Hmmmm. This is sort of a travesty, so I added content CSS to print the words "non-public/access filter only" next to lock icons. It's a mouthful, shows at the wrong line height and doesn't wrap well on mobile edit: fixed (I'll work on all that soon - I just wanted to get a working example online, asap, so it's viewable and looks like...this).

If I ever get involved in reporting DW things again - which I like to say I never will, but only until another bug rears its head, like the one I stumbled over today (possible bug: all of our usericons have the same image number, so you can't download and save more than one of them without overwriting the last one downloaded - not unless you rename the next one before saving, which I don't *think* is the correct behavior!) I might post a Suggestion asking for access filter text to display next to access filter icons.

If adapted it would mean printing more stuff to the page, but could save quite a few "oops" moments sitewide (or at least minimize them, as there's no fixing people who just won't pay attention) so it might be worth doing, not to mention having actual text (as opposed to merely alt text) reading out from a screen reader to indicate what sort of post you're on might make the experience somewhat smoother all-around.

marahmarie: my initials (MM) (Default)

Dreamwidth was unintentionally DDosed by someone's homework a few weeks ago. And no, you can't make this stuff up: Tonight's intermittent 404's.

While I was busy being mostly unable to use the site (along with [personal profile] conuly, whom I was having a comment exchange on this DW with at the same moment said homework went on a rampage) I hit upon a few DW pages that thanks to our CDN (CloudFlare) had been converted on-the-fly into read-only, which lets us view the site without actually being able to use it.

Fascinated, I studied the read-onlyness of them while exchanging replies with someone on an Anti-AOL post about AOL shutting off their News comment sections, which occurred approximately eleventy bajillion years ago but somehow is still news. The person replying was in a pique that comments to that post were less than, shall we say, civil.

For her, this included comments from my commenters (who think my blog is officially sponsored and run by AOL, and who therefore address the blog owner - that is, me - as though I'm not only an AOL employee, but also like I'm The Reason Why They Can't Have Nice Things) and comments from me, because I don't enjoy people still thinking I work for AOL after telling them a thousand times a second that no, I don't.

After exchanging a few comments with her (she was actually rather nice, which I appreciated) I looked back at DW's Support page, which I was also trying to reach while it was set to read-only, so thanks specifically to DW's homework DDoS Anti-AOL is now (permanently) read-only, because while I was waiting for DW to get un-DDoSed I shut comments off, just like they did over at AOL News.

If you're a Wordpress.com blog owner who wants to completely disable comments, it's not that hard, just time-consuming. Step 1: Log in, go to WP admin and disable comments. Step 2: Screen all publicly visible comments - that's it. It took a while because WP.com's admin is 1983 dial-up slow and you can only screen one pageful of comments at a time.

The way I did it (I'm not sure if there's a sorting option or if having one might help) newest comments screen first, which gave me a nice, chill walk down memory lane back to when Anti-AOL was on LJ and nearly no one thought I worked for AOL and sometimes I miss the hell out of just being thought of as myself but oh well, the blog will be 12 years old this November and I stopped having anything constructive to say about AOL years ago.

marahmarie: my initials (MM) (Default)

Firefox actually has the weirdest performance in some areas:

  • clearing comment forms on entry pages (the whitespace between entry and form works as it should in _every_other_browser_; in Firefox the form doesn't clear by more than a few pixels unless I about triple the top margin).
  • arranging cell space on comment forms under 360px width on mobile is not going very well (our comment forms are actually tables nested within tables, which doesn't make it any easier)
  • displaying padding in text fields (for example, the search box in the navigation bar above the header is the wrong shape/size in _every_other_browser_ because Firefox)
  • certain CSS properties/values work in Firefox but in no other browser, which led to this thing today where my comment forms looked like someone shook all my pages really hard and let the form fields land where they would. Such fun.

I think I'd need about a thousand hacks for every possible browser/OS/device configuration to work around some of this, or to simply hack Firefox to allow better display in other browsers. And I could hack Firefox, because there are hacks for it.

The other thing is how needless it is to test page display on multiple versions of modern Webkit (only speaking of Windows browsers). If you check a web page in Chromium or Google Chrome, it seems you've checked it in every modern Webkit browser including Safari for Windows - which stopped at v.5 some years ago - except modern (non-Presto) Opera, which has its own ideas about CSS.

I'm not sure if this applies to Chrome on Android, as well, but as far as desktop testing goes, yeah, it does seem that way.

marahmarie: my initials (MM) (Default)

I do actually have a Support Request in over this. From the tl:dr: at the end of it:

"the Upload Images page should have uploaded images set to the same security as one's journal is by default, which should match the security shown on the Manage Images page, but because the upload page defaults to "public" on the dropdown, the last 3-5 images I've uploaded from DW and posted publicly, both to Support Staff and on my own DW were locked to access-only and I didn't know it, since I haven't viewed any of these pages while logged out of DW."

ETA: I closed the original Support Request and opened another after getting feedback in the comments below saying that the first request was not worded clearly enough.

All pictures I think I've set to public should now be public at this point, as I just went through my last few weeks of image uploads to make sure. My apologies to anyone who was like, "Huh" and just stopped reading because there was no image to carry the point(s) I was trying to make in whatever post(s) you came across in this condition.

Now y'all have learned I don't look at my own DW logged-out often enough to catch these things, which is maybe not the greatest fact to share with whoever runs across this, but anyhow...

marahmarie: my initials (MM) (Default)

...what? *side eyes Issue 2119 (from related code tour)*

Actually happened. To me. At the time, though, that was *not* what I thought had uh, happened *winces*. And no, reading through the pull request, I see I'm not the only person who's been bit by this bug (following it back to the original is actually pretty interesting, as the bug responsible for it was alive and kicking 16 years ago).