Email or username:

Password:

Forgot your password?
Zach Leatherman :11ty:'s posts Post Back to profile
Top-level
Rijk 🐰 ✨

@zachleat Apparently it's so new it makes the DevTools crash 😳 (In Arc, which is Chromium based)

26 August at 22:26 | Wall-to-wall | Open on fosstodon.org
10 comments
Zach Leatherman :11ty:

@rijk yeah! crashes every time I inspect in Chrome Dev Tools too 😬

cc @paul_irish

26 August at 22:28 | Open on fediverse.zachleat.com
Ricky de Laveaga

@zachleat @rijk @paul_irish also only *works* in Chrome correct? Is Safari or Firefox support even on the horizon? Does @eleventy care about non-Chromium browsers?

27 August at 4:23 | Open on mastodon.social
Ricky de Laveaga

@zachleat @rijk @paul_irish @eleventy seems like a wrapper element that works in all browsers is vastly preferable.

27 August at 4:30 | Open on mastodon.social
Zach Leatherman :11ty:

@rdela @rijk @paul_irish @eleventy I suppose it’s my fault for not communicating the amount of nuance in play here. Make sure you test in Firefox/Safari to see the fallback behavior!

27 August at 13:27 | Open on fediverse.zachleat.com
Ricky de Laveaga

@zachleat @rijk @paul_irish @eleventy I did test, see other response. Also I tried to have a conversation about this here mastodon.social/@rdela/1129740

…on GH github.com/rdela/eleventeen/pu

…and emailed you about it as well, Zach, to no avail. I get that the wrapper element isn’t your preferred choice here, but when even devtools is crashing, it became almost comical to me, so I thought I would chime in here as well.

27 August at 20:35 | Open on mastodon.social
Zach Leatherman :11ty:

@rdela @rijk @paul_irish @eleventy Not sure why this feels like a heated discussion—I am back from vacation and haven’t quite caught up on all my emails yet?

Unfortunately I don’t think the container element *is* preferable—it has markup and styling complexities that I’m trying to avoid (if possible!).

27 August at 20:54 | Open on fediverse.zachleat.com
Rijk 🐰 ✨

@rdela only works in Chrome *at the moment* as they're the first ones to ship it. It's a w3 spec just like any other so it'll come to other browser soon enough. The way @zachleat implemented it means it's a progressive enhancement for browser that have it already, but it won't break or lock things down for other browser that don’t. 🙂

27 August at 13:29 | Open on fosstodon.org
Zach Leatherman :11ty:

@rijk @rdela just to be super clear, the links are still positioned visually the same in other browsers, it’s just with less ideal markup

27 August at 13:32 | Open on fediverse.zachleat.com
Ricky de Laveaga

@zachleat @rijk The links only show on hover now, a huge downgrade for both accessibility and discoverability. Also iOS Safari seems severely broken and doesn’t even show the links when you tap on the heading, not that I understand why one would, since there is no indication they are tappable.

27 August at 20:29 | Open on mastodon.social
Rijk 🐰 ✨

@rdela @zachleat While valid concerns overall, those aren't a result of using anchor positioning which kicked this thread off. You can see the same behavior in the previous iteration that didn't use the newly released CSS property eleventy-base-blog.netlify.app

27 August at 20:33 | Open on fosstodon.org
Go Up