@danbri @sw12 @agektmr Somewhat the same experience here. Especially “afraid†of autofill up-filling (i.e., retouching things I entered before). Down-filling (i.e., pre-filling things I haven’t touched before) is mostly fine, albeit still subtly wro
RT @stefanjudis: Chrome 89 comes a bunch of useful @ChromeDevTools additions but I’m mostly excited about the new Puppeteer recording butto…
RT @edent: Here’s an interesting take on Footnotes in HTML from @tomayac
https://t.co/QShuGUrDwE
@justmarkup Thanks for the inspiration: https://t.co/XL1vn9Upv8. I would never have considered using the `ruby` element without your tweet. ðŸ™
@edent That’s interesting. Especially since Firefox is the only browser at the moment to support `ruby-align`. I wonder if by making the footnote text display block it’d look better, maybe in combination with different values of this property?
@chriscoyier, since you had thoughts on @edent’s `<details>` footnotes (https://t.co/caGf8GuSAB), I’m wondering what you think of `<ruby>` footnotes. Also, any CSS trick up your sleeve regarding my identified presentational shortcomings: https://t.co/XL1v
🔢 New post: `<ruby>` HTML footnotes:
“`html
Lorem ipsom
<ruby>
dolor sit amet
<rt>
Lorem ipsum is a
chopped-up version of a real work;
you can’t truly translate it.
</rt>
</ruby>,
consectetur adipiscing elit.
“`
Read on [1].
â€
💂 I’m very interested in the thoughts of experts of CSS (Can the rendering be improved?), accessibility (Does this work well with screen readers?), and HTML (Is this abusing `ruby`?). Also HTML elders (@draggett, what happened to `FN`?). I mention prio
Interesting: WebXR (https://t.co/qUpBCwfArc) was added to the â¦@webkitâ© status tracker as officially “in developmentâ€. https://t.co/TNXvJ3H2df