Maciej Stachowiak 🇺🇸🇵🇱❤️🇺🇦 @othermaciej@qoto.org

I have changed my music genre for max flow state productivity from Goa Trance to Phonk.

@TheFake_VIP GNOME Web (formerly known as Epiphany) is probably the second most notable WebKit-using browser (besides maybe various iOS browsers which use the system WebKit).

I feel good about the way Poland has stepped up to support Ukraine during Russia’s invasion. But sometimes I see stuff like this and I am ashamed. And I’m happy I live in the US where the First Amendment forbids banning speech just because it offends someone’s feelings. https://notesfrompoland.com/2023/04/21/court-convicts-women-for-offending-religious-feelings-with-rainbow-virgin-mary-at-lgbt-march/

@tomayac @jensimmons @jondavis it should be shipped, given the date of landing. We wil look into it.

@tomayac @aardrian @mathias I was responding to your Mastodon post, which just said “Select the H1 and copy. On the clipboard:”, nothing about where it’s pasted.

Nitpick: for a valid test in Firefox you have to use inline style, due to the (apparent) bug where they don’t put style from non-inline style on the clipboard at all, not even in HTML format or in properties. With inline styles, they do the thing you want for plaintext but not rich text paste, which is what the spec asks for.

@tomayac @aardrian @mathias Hmm, I think Firefox behavior may be partially a bug. Firefox will copy this as all uppercase to rich text contexts but sentence case plaintext: `<h1 style="text-transform: uppercase">Hello<h1>`. But the original example it copies as mixed-case always. So it's following the spec rule for plaintext, but additionally has a bug where it won't copy styles that come from style rules, even when pasting into an editable HTML context like a macOS Mail compose window. Firefox likewise copies `color: red` when it comes from inline style but not when it comes from an external style rule.

@tomayac @aardrian @mathias The spec only requires this for plain text paste, not any other format, so you may or may not have seen a spec violation depending on how and where you pasted.

That said, I think this spec requirement for plain text paste is bad UX and should be changed in the spec. Users expect that when they copy/paste, they get the same characters. They have no way of knowing which capitalization is stylistic vs part of the content.