ETA13 8-13-23 9:18pm: You can read the new support request here. I closed the last one shortly after submitting it last night when I realized there were even more things wrong I hadn't seen until "roughly the same minute I submitted it" along with things I knew were wrong that I simply forgot to fully check into because yay hi yes, me.
You can safely ignore anything below this line unless you really want to pick through some damn weeds with me - which only tells part of the story, anyhow.
*feel free to ignore*
It didn't look like this last night around this time. Now it looks like Notepad *squees*
Color-coded aka syntax highlighting:
I like the line numbering especially.
Only off things I notice are the textbox is about half the height it used to be and is missing the thing. You know the thing, the semi-triangular thing with three lines in the lower right corner that you can pull on to make the textbox bigger? That. What is it called? An expander? It seems to be missing.
ETA1: It's also missing a scrollbar. Up and down arrows, here I come. Eh.
ETA1b: The scrollbar only appears if I start scrolling by using the up or down arrows. If I don't put a cursor inside the textbox and start using it, there's no scrollbar.
(Seeing this is on desktop Firefox 115.0.3 64-bit/Windows 11 with Fx extensions enabled; haven't tried disabling extensions nor tried this in other browsers and/or on mobile.)
ETA1c: restarted Firefox in Safe Mode/aka Troubleshooting Mode - all extensions disabled, with cache, cookies and history deleted: still no scrollbar (no expander, either). A super-thin black scrollbar appears as the page loads, only to disappear as soon as I try to grab it with my cursor.
Again once I use the up or down arrows within the textbox the scrollbar becomes visible and stays visible and usable from there on out.
ETA2: Another issue seen in Troubleshooting Mode: The old style textbox flashes in on page load, only to be overlaid/overwritten by the new style as page load finishes. Disconcerting.
Also why I decided to use Troubleshooting Mode tonight as I thought I'd seen that with extensions enabled and almost worried it was my ancient Web Dev extension or even my actual copy of Notepad infiltrating into the textbox somehow.
ETA3 3:00am: Think I might've figured the scrollbar issue out upon noticing just now that Chris Pederick's Web Dev extension for Firefox does the same thing. That tells me the problem's endemic to Firefox alone and/or Firefox perhaps solely on Windows 11. Without testing other browsers/OSes I can't be sure but I got a feeling.
It's possible (though I can't say without examining add-on source/DW backend code) both Chris and Dreamwidth went with unstyled scrollbars. In Firefox those might take system default styling and my guess is system default styling's not working right on Windows 11, with Win11 being perpetually in beta and all. Just maybe my not so wild guess.
ETA4: Guess it'd be helpful to mention I'm not and wasn't using Canary (a bleeding edge release of Dreamwidth available to beta testers that I didn't know existed until about an hour ago) when I encountered the above oddities.
ETA5: We can no longer use the browser Find function to find CSS within the textbox. So to find anything you wish to change once it's in there you have to Ctrl A then paste it somewhere else just to find it.
And I know without even poking at it this'll be because of ETA2: old style textbox flashes in on page load/refresh to be replaced by new style textbox once page load completes. The entire box is not real, nor anything in it. It's all being pumped in via JS. Grrrrr.
ETA5a: Confirmed! Just turned browser JS off and refreshed the page and sure enough got the old textbox back. At least now I know how to find a usable one.
If it was going to have this little functionality right out of the box it should've been offered up as a Beta tester option.
ETA6: "To insert indentation or open the code hint menu, press Ctrl + m" doesn't work, either. I'd say "no longer works" but I've never tried Ctrl+M before so I can't say.
That said, I want to cross-browser test the new textbox style before I submit anything. Another time, I guess.
ETA7, 8-13-2023: Sooooo happy. Submitted a support request tonight for the Firefox scrollbar issue as I see it on Win11, then realized I still have a tower running Win10 and couldn't replicate the issue on it, so my original hunch was right - it's a Win11-not-playing-nicely-with-Firefox issue, yay.
And with further testing I see Firefox's Find works in every browser I tested (see support request for my list) except for Firefox on Win11 where Adblock Plus interferes with it somehow.
My laptop runs Win11. I do 100% of my CSS edits and updates from it. And edit my CSS a lot. I usually only post changes after code pushes where global journal style changes wind up affecting how I do things, so maybe a few times a year, as ever since creating Pride I don't much want to change my style anymore.
That said, unless/until DW dev fixes the scrollbar issue I've found I can just disable Dreamwidth's JS and scroll and Find same as before the JS overlay got added.
ETA7a, 8-13-2023: closed the Support request as I just saw our Perl compiler's having the same scrollbar issue in Firefox on Win11, then realized I forgot to check textbox expanders for their very existence or lack thereof in any browser tonight to see if that's still an issue. The scrollbar is a an important issue by itself (usability, accessibility) but I'd rather roll all issues/all instances (CSS editor, compiler) into one request.
Will update with a new Support request link when I get another chunk of time to look at this.