[13:16:51] i was getting this aswell btw [13:16:53] on every refresh [13:32:17] link? [13:37:29] https://superstarracers.wiki [13:39:03] [1/2] Looks fine for me [13:39:03] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1421853718281719818/image.png?ex=68da8bf7&is=68d93a77&hm=256b0723cfca87dfb23e4cedfb9c994d8354403c8ff6fa77d97d8ac512096553& [13:39:48] Might have been caching [13:54:22] This reminded me that DarkMode also pushes iframes to the front and you can't manipulate them to render under the non-iframe HTML elements using `z-index` for uh, reasons [13:54:51] Are you sure that's caused by dark mode? [13:54:59] Sounds like that's done for security reasons [13:55:12] As a countermeasure against phishing [13:56:49] I remember having a Discord widget setup on Mirage that I wanted to be rendered under the Mirage navbar/dropdown menus. Worked fine on Light Mode but the moment I turned DarkMode the Discord embed would immediately just render above the menus [13:57:10] This was on like April tho. Our wiki doesn't even enable Mirage anymore [14:02:44] More to the point of excluding DarkMode as a default extension, I (and I'm sure most other people) definitely didn't realize that DarkMode was just a "apply `filter: invert`" hack than an actual functional DarkMode, so I'd be in favour of disabling it