Archive of Our Own

Notes:

Well, I learned something here: be careful with your left: value; all of the positional declaration properties can be a little finicky (and one must check multiple devices!), but man, that one turned out not to be a good idea to set to -200em, because even though I gave it a width of -200vw (notice the change there?), it didn't block out the screen on my iPhone or my Android, even though everything was hunky dory on my desktop's Chrome, Firefox, Opera, Edge, and Tor.

Me, I'd go with ?style=disable, but that's not everyone's cup of tea, granted; the other was a new tab and enabling a site skin that automatically disables creators' styles (or targets this work specifically, or/or/or) and then refreshing this page, though of course simply viewing the page source would let you see things before they happen, and inspecting the elements would let you — ahem! — see the invisible — AHEM! — (but where's the fun in that, I ask you, without first puzzling things out?). 😉  I would say more... hmm... oh wait, I do believe that I did... now where in the world could that be...

...and then there are those who just love to complicate things.... (if you can read this, comment “Jedi”! 🤣)

Hax the w0rld, man! ❤️

---

NB:  2 hours and 23 minutes after I uploaded this chapter, I finally got the notification, so if any of my subscribers are wondering why I was seemingly an hour and more late with this morning's chapters in everything (and last week's chapter in the latest Peach/Zelda & Sonic fic.), then heads-up: it was the same thing then, too. 🤔  I will presumably upload next week's second chapter of The Futa Plague at my usual Sunday 10:30 CDT (15:30 UTC), but I make no guarantees as to when (or if...) you'll get the notification.

---

BELATED EDIT FOR SPECIAL NOTE:  When doing some OTT work like this, just as always, but in this case more than ever... check your results on multiple browsers with multiple aspect ratios, then check it across multiple devices (and on 'phones, turn them sideways for portrait vs. landscape), and scroll top-to-bottom AND side-to-side, and then do all of this again in Low Vision Site Skin because it completely alters the height of things such as the screen top position and just how far down the bottom banner really is, and then maybe try it all again-again in Reversi and all other site skins if you have any special colors involved — and don't be surprised when you do find out that you messed something up somewhere as viewed in some skin on some browser with some device at some ratio... and find out again that something else is now wrong due to fixing the first dozen things, and then again, half a dozen more times (and since I haven't tested this on a big-screen TV as a display... I can guarantee that some of you have breezed right through this and wondered what my apparently-empty braggadocio was about — well, you can be my guinea pig: go try it again with your browser shrunken to anything like a normal monitor size or smaller, and lemme know if there's a difference).

...ask me how I know... 🙄

  I'll let you in on a little secret, if you promise not to tell anyone else: half of the crazy numbers that you see in my work skin?  Sure, some are conscious design, but most are forced to be enormous due to the ridiculous layout changes named above THAT YOU NEED TO CHECK.  And I guaran-damn-tee you that that's exactly what drives many other works' crazy-looking choices.

OOH!  I flaked, and didn't add this here a few weeks ago when I tumbled to it, instead only using it in some fic.s that really needed it and adding it to the Targeting tutorial.  Different site skins (open that in a new tab and test them all vs. this chapter) dick with even some of AO3's official classes' bg and font color, but the <div class="caution"><div class="draft">combo [caution OUTSIDE of draft, not inside] seems to be safe against the official skins anyway</div></div>!

(See the end of the chapter for more notes.)