4 ms·

I stopped reading when it said this was behind a browser flag. Was I wrong to stop reading; is there a better story than that? I've been doing CSS long enough

by xrd 4y ago

I stopped reading when it said this was behind a browser flag. Was I wrong to stop reading; is there a better story than that? I've been doing CSS long enough to know that to get things work you often have to work with what you have and that means wrapping things inside (otherwise) redundant containers, etc. Using a polyfill is less than ideal, but at least I have control over including this. And, it says it is under development, so I didn't even want to use that. But, asking my users to enable a browser flag? That's a non-starter. I'll file this under something interesting to revisit in a year or two.

pancrufty 4y ago
Uhm, this is a preview. You’re not supposed to use it until it’s widely available. They’re just showing it off and gathering feedback. > I'll file this under something interesting to revisit in a year or two. Correct. However things are moving fast so certain new features become widely available within months.
- londons_explore 4y ago
  > available within months. Unless you need to support iOS... In which case, wait a few years because we can't have the web platform being too effective compared to apps...
  - micromacrofoot 4y ago
    They've been very quick at implementing CSS changes in Safari, faster than Firefox in some cases, but yeah bigger web APIs like push notifications have taken too long
    - londons_explore 4y ago
      Perhaps because CSS is entirely a programming task within the rendering engine... But Web Push requires changes from the whole browser, perhaps minor changes to the OS, and probably a whole server side implementation. And with all that cross-team effort going on, it's very easy for management to deprioritize it.
      - micromacrofoot 4y ago
        That seems like a good guess. I'd also guess that there are a lot more internal politics involved when they're implementing OS-integrated features that are easy to abuse. There are a lot of sites that ask for notification permission that definitely don't need to, and that probably saps some of the motivation for implementation at Apple. It's frustrating for developers with completely valid use cases, frustrating for open web standards, but I can understand being overprotective of user experience. It's a difficult balance.
tgv 4y ago
You're completely right. It's a kludge for attaching elements in a page structure that wasn't designed for it, and of course it's Chrome only.
- megaman821 4y ago
  I mostly do web development. Is there a UI framework that really nails this pop over and alignment problem that you have in mind?
  - ErikHuisman 4y ago
    https://tetherjs.dev https://tetherjs.dev
jefftk 4y ago
> I'll file this under something interesting to revisit in a year or two. That's fine to do if you're only interested in "is this a thing I can use now" (no, not yet). But if you care about how the feature is designed and are worried that they might get it wrong, now is the time to read the proposal and speak up!
ajkjk 4y ago
Generally stopping reading over a small complaint is, yeah, pretty petty.

by xrd 4y ago

pancrufty 4y ago

Uhm, this is a preview. You’re not supposed to use it until it’s widely available. They’re just showing it off and gathering feedback. > I'll file this under something interesting to revisit in a year or two. Correct. However things are moving fast so certain new features become widely available within months.

londons_explore 4y ago
> available within months. Unless you need to support iOS... In which case, wait a few years because we can't have the web platform being too effective compared to apps...
- micromacrofoot 4y ago
  They've been very quick at implementing CSS changes in Safari, faster than Firefox in some cases, but yeah bigger web APIs like push notifications have taken too long
  - londons_explore 4y ago
    Perhaps because CSS is entirely a programming task within the rendering engine... But Web Push requires changes from the whole browser, perhaps minor changes to the OS, and probably a whole server side implementation. And with all that cross-team effort going on, it's very easy for management to deprioritize it.
    - micromacrofoot 4y ago
      That seems like a good guess. I'd also guess that there are a lot more internal politics involved when they're implementing OS-integrated features that are easy to abuse. There are a lot of sites that ask for notification permission that definitely don't need to, and that probably saps some of the motivation for implementation at Apple. It's frustrating for developers with completely valid use cases, frustrating for open web standards, but I can understand being overprotective of user experience. It's a difficult balance.

tgv 4y ago

You're completely right. It's a kludge for attaching elements in a page structure that wasn't designed for it, and of course it's Chrome only.

megaman821 4y ago
I mostly do web development. Is there a UI framework that really nails this pop over and alignment problem that you have in mind?
- ErikHuisman 4y ago
  https://tetherjs.dev https://tetherjs.dev

jefftk 4y ago

> I'll file this under something interesting to revisit in a year or two. That's fine to do if you're only interested in "is this a thing I can use now" (no, not yet). But if you care about how the feature is designed and are worried that they might get it wrong, now is the time to read the proposal and speak up!

ajkjk 4y ago

Generally stopping reading over a small complaint is, yeah, pretty petty.