Gregory's Server@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?
|
8 comments
 @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! @zachleat @rijk @paul_irish @eleventy I did test, see other response. Also I tried to have a conversation about this here https://mastodon.social/@rdela/112974024986394224 …on GH https://github.com/rdela/eleventeen/pull/44 …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. @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!). @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. 🙂 @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 https://eleventy-base-blog.netlify.app/blog/thirdpost/ |
@zachleat @rijk @paul_irish @eleventy seems like a wrapper element that works in all browsers is vastly preferable.