Browser-compat-data: Data with "This value is recognized, but has no effect." should be shown as not supported

Created on 15 Jan 2018  路  1Comment  路  Source: mdn/browser-compat-data

Currently there are some data with { version_added: true, note: "This value is recognized, but has no effect." } in css.properties.align-content and css.properties.justify-content

I think it's normal that if someone sees a "Yes" on a compatibility table, they think they can use the feature. But in fact it doesn't work.

I suggest we set the version_added to false until these browsers truly support them.

One more thing, Edge also recognize some value (but has no effect), they need to be updated.

data good first issue help wanted

Most helpful comment

It is a bit more tricky than this as even if a feature "does nothing", the fact that it is supported may alter some side behaviour.

{
  justify-content: space-evenly;  
  justify-content: start;
}

has "No effect" on a browser that supports start but doesn't apply an effect.
But will behave as space-evenly for a browser that doesn't support start at all.

So we need to store the distinction.

I think using false in such cases is even misleading, although I agree that the current message is a bit light. Maybe we should use partial_implementation for these cases?

>All comments

It is a bit more tricky than this as even if a feature "does nothing", the fact that it is supported may alter some side behaviour.

{
  justify-content: space-evenly;  
  justify-content: start;
}

has "No effect" on a browser that supports start but doesn't apply an effect.
But will behave as space-evenly for a browser that doesn't support start at all.

So we need to store the distinction.

I think using false in such cases is even misleading, although I agree that the current message is a bit light. Maybe we should use partial_implementation for these cases?

Was this page helpful?
0 / 5 - 0 ratings