Alpha channel support in x265 is very interesting, as this was only previously possible with paid-for Apple software (and the resulting file sizes were high). Some details from when I last looked at it https://jakearchibald.com/2024/video-with-transparency/#enco...
Readit Newsjaffathecake commented on FFmpeg 8.0 code.ffmpeg.org/FFmpeg/FF... · Posted by u/gyan
jaffathecake commented on A gentle introduction to anchor positioning webkit.org/blog/17240/a-g... · Posted by u/feross
Yeah I could have mentioned the actual issues I had.
My first attempt was to anchor an element to another one that occurred later in the document order, and it didn’t work. The anchor must be placed before any of its dependents. It kind of makes sense, but doesn’t jump out as intuitive.
That document order thing doesn't sound right to me. Here's a demo where the popover appears before the anchor https://codepen.io/jaffathecake/pen/MYargba?editors=1100
jaffathecake commented on A gentle introduction to anchor positioning webkit.org/blog/17240/a-g... · Posted by u/feross
Would be cooler if the whole system were more flexible: you simply define 2 anchor points (one on the target, another on the source, so center bottom would be bottom width 50% and top width 50%) instead of being limited to the 9 predefined areas
`position-anchor` is a high-level simple way of doing it, and it comes with the restrictions you mention. However, the `anchor()` function, which is also mentioned in the article, gives you the kind of flexibility you want.
jaffathecake commented on A gentle introduction to anchor positioning webkit.org/blog/17240/a-g... · Posted by u/feross
Anchor positioning sounds cool, but I ran into some very unintuitive behavior when I tried to use it. Can’t remember the details, it was a couple years ago.
I guess you're being downvoted as a general nay-sayer, but you're right. I tried this feature last month and a bunch of browser bugs and design issues got in the way. I reported them, and they're being worked on https://github.com/w3c/csswg-drafts/issues/12466
The `margin:0` issue was particularly frustrating & imo should have been covered in the article, as it's a real gotcha when trying to use popover & anchor positioning in combination.
jaffathecake commented on Who has the fastest F1 website (2021) jakearchibald.com/2021/f1... · Posted by u/tosh
Missing Mercedes and Alpine, odd that the original post didnt have it either
> odd that the original post didnt have it either
Totally honestly, it was a lot of work, I got bored, and it was diminishing returns for the later parts.
> I see good, smart people, who'd always avoid using "click here" as link text
Links to: https://www.w3.org/QA/Tips/noClickHere
> contributed Sep 2001 by Aaron Swartz
RIP you're still remembered
I linked to it without realising that. I didn't know Aaron personally, but I remember people speaking fondly of him.
The entire point of footnotes is that they have been moved out of the main text because their presence would negatively impact the flow. If most readers are expected to want to read them then they should just be part of the text and probably not even in parentheses.
Right, but it should be easy for the reader to decide whether to divert to the additional content. A superscript number tells you nothing about the additional content. Whereas on the web, link text or a details summary can help you make a decision.
For footnotes/sidenotes/endnotes, I think about a few implementations:
- Dorian's expandable parentheticals (click on the gray phrases): https://doriantaylor.com/person/dorian-taylor#me
- Gwern's list of sidenote implementations: https://gwern.net/sidenote
- The ellipsis -> bottom modal pattern, found on buttondown articles like this one: https://buttondown.com/hillelwayne/archive/you-can-cheat-a-t...
These days, I try to remove tangents from my writing, publishing any good tangents as microblog content instead.
I'm also considering unhyperlinked footnotes, and letting the reader scroll to the bottom if they want, the low-tech way. It's less distracting that way, and there's no accessibility issues either.
There are absolutely accessibility issues https://adrianroselli.com/2022/09/brief-note-on-super-and-su...
I'm a big fan of sidenotes as a solution for this. If you're on desktop they'll pop out to the side and it's easy enough to glance over at them or stay focused on the main text without having to navigate around. On mobile that obviously doesn't work, but instead you can just have them open inline, so you don't have to deal with the annoying anchor link jump behavior and remembering where you were. And it's all doable with CSS and float, no Javascript!
Here's an example with a fair number of sidenotes:
It's ok, but you're still being taken out of the flow. Especially as the notes appear arbitrarily on the left or right. And yeah, you have to find your place again afterwards. It's way better than scrolling solutions though.
That particular example on mobile falls back to a revealing pattern, which is pretty good.
It still has the problem where it's just a test of your curiosity. You don't really know what the supplementary content covers until you expand it. The link text is just a superscript number which is kinda useless.
This is why I prefer the solutions in the article where the supplementary content has a heading that hints at the content.
You are right, thanks. Ironically, I didn't realize that because I only read the text:
> If the footnote markers are links, then the user can use the back button/gesture to return to the main content. But, even though this restores the previous scroll position, the user is still left with the challenge of finding their previous place in a wall of text^6.
and didn't read footnote 6, which mentions the technique I'm describing. But I still don't seem to see the UX issues, other than the mention of a teeny-weeny hit target, which I admit is perfectly legitimate. But I am an academic, so it is probably no surprise that imitating academia appeals to me.
The other issue is the poor link text (a superscript number) which gives no clue as to the content at the other end of the link. Like I said, it just becomes a test of your curiosity. Whereas the other examples have headings relevant to the content.