Notices by Nolan (nolan@toot.cafe), page 31

@mdm It may be my eyes deceiving me, but that looks like just an opacity filter? Compare to Firefox and Chrome, which ought to look similar. Here's a screenshot of that same profile in Edge 17 and Safari 11, which do support backdrop-filter. https://toot.cafe/media/dBNqy3nYiSpdV1bBNrg https://toot.cafe/media/Q1ANWPjRvOo2ELVk4ms

@paeneultima @grainloom Yeah, agree it's a bit painful atm. On the backlog. :) https://github.com/nolanlawson/pinafore/issues/11

@sina @Alamantus I took a look at Mastodon's own dark theme and it appears to use black-on-white for textboxes as well… So this may have been intentional. I didn't actually write the dark themes though. :)

@Alamantus Welcome! ☕

@rowan Done! :sadglasses:

@mdm Sometimes the trajectories are similar because we're both largely tied to the OS. So my hunch about backdrop-filter is that it was easy for us to implement, since we only have to implement it for Windows, and ditto for Safari who only really needs to worry about iOS/macOS.

Although the WebKit team does also still maintain Windows/Linux versions IIRC, so not sure how that figures into their prioritization. It'd be interesting to see if Epiphany browser on Linux supports backdrop-filter. 😊

BTW I have nothing against CSS-in-JS as an authoring format; it just never made much sense to me as a format to actually deploy in production. The browser has to parse the CSS twice (once as JS strings, once as CSS), which is a perf cost. Also it makes CSP for inline CSS difficult.

Looks like mini-css-extract-plugin may be the Webpack async CSS behavior I've been dreaming of. It works by extracting CSS as (get this) actual CSS files! https://github.com/webpack-contrib/mini-css-extract-plugin

That means no more CSS-in-JS, which has already shaved ~70kB off of Pinafore's total JS size. Also there aren't dozens of inline <style> tags, meaning I might be able to eventually restrict inline CSS via CSP. https://github.com/nolanlawson/pinafore/pull/145

@loke Did you revoke the token for your login to the instance? If you look in the Dev Tools in the network tab you may see what the actual network error was.

@KitRedgrave It depends. Sometimes stuff should run in parallel, so it makes sense not to `await` in serial. E.g. here's an example from Pinafore where I want to kick off a network request early, but then also wait on a local IndexedDB call: https://github.com/nolanlawson/pinafore/blob/7b848db140b3766cdb8f55eee174ac4acf3cce28/routes/_utils/sync.js#L1-L18

@grainloom The pictures are sometimes kinda big, so I did this as a compromise. Maybe I should make the header visible when you hover the non-frosted area though, hmmmm...