You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you think there's a case where we'll want to start collecting developer signals for a feature that doesn't yet exists? I'm thinking of masonry layout as an example. Of course, it exists now, but it used to be a thing developers wanted to do long before Mozilla experimented with it in CSS Grid. What if there's a feature like this that has already received developer signals via things like CSS WG issues, surveys, or other, but which isn't yet tracked in the web-features repo?
The text was updated successfully, but these errors were encountered:
Do you think there's a case where we'll want to start collecting developer signals for a feature that doesn't yet exists? I'm thinking of masonry layout as an example. Of course, it exists now, but it used to be a thing developers wanted to do long before Mozilla experimented with it in CSS Grid. What if there's a feature like this that has already received developer signals via things like CSS WG issues, surveys, or other, but which isn't yet tracked in the web-features repo?
The text was updated successfully, but these errors were encountered: