Skip to content

Conversation

@kiding
Copy link
Contributor

@kiding kiding commented Dec 13, 2018

IE9 and Firefox 3 have been considered "partial support" due to the note 1 and 2, respectively. The other notes 3 4 5 are not much different from 1 and 2, so the corresponding browsers should also be "partial support."

Technical rationale

…ld be too. See the pull request for more rationales.
@Fyrd
Copy link
Owner

Fyrd commented Dec 18, 2018

It's often tricky to decide what counts as partial support and what's just a bug...the reason it's the way it is is because I believe the "input" event on text fields is significantly more useful and used by developers than the event is on those other fields (where the "change" event works well enough).

Because of this, to save developers from spending time figuring out why support for most browsers is "partial" it's just considered a bug for the other fields.

Do you have reason to believe the bugs are significant enough to warrant partial support?

@kiding
Copy link
Contributor Author

kiding commented Dec 18, 2018

Thanks for the comment. I have a feeling this might be blown into a totally different one, but nonetheless here are my thoughts.

I do understand where your thoughts come from. However, to me the reason itself sounds a bit arbitrary and specific only to this feature. How much of a feature should a browser support to be considered a full support? How much usage should that specific portion of a feature have? Maybe we should gather the usage data to determine the threshold... These questions are so tricky to answer, and the solutions themselves get too much complicated.

Personally, something that shows "Partial Support" has been an immediate yellow flag (quite literally) that forces me to learn more before writing any more code. I believe that the immediacy—and the repulse that follows—is what makes Can I Use incredibly useful to web developers. This case as an example: Those who implement <input type=file> with input event simply can not avoid spending more time if they want cross-platform support. Coming back to debug would be tedious enough, but wouldn't it be nice to at least show it more apparently right away?

I think the issue boils down to the fact that "Partial Support" is somewhat ill-defined. In my opinion, a browser supports a feature "partially" when it omits a sub-feature of a given feature, where the feature itself is described by the reference specification, which might change over time. The feature has "a bug/issue" when the implemented sub-feature behaves wrongly or erratically (returning unexpected results) or maybe differently (unlike other browsers). I see most of the features on Can I Use already fit this definition. Some features that came all the way from the old days of no spec at all would be very tricky for sure though.

I'd love to hear any thoughts on this. I hope my intention went through the language barrier intact.

@kiding
Copy link
Contributor Author

kiding commented Jul 11, 2019

"notes_by_num":{
"1":"Partial support refers to [a bug](https://bugs.chromium.org/p/chromium/issues/detail?id=773041) where long lists of items are unscrollable resulting in unselectable options.",
"2":"Partial support in IE refers to [significantly buggy behavior](https://web.archive.org/web/20170121011936/http://playground.onereason.eu/2013/04/ie10s-lousy-support-for-datalists/) (IE11+ does send the input and change events upon selection). ",
"3":"Partial support refers to no support for datalists on non-text fields (e.g. number, [range](https://bugzilla.mozilla.org/show_bug.cgi?id=841942), [color](https://bugzilla.mozilla.org/show_bug.cgi?id=960984)).",
"4":"Partial support in Edge refers [to disappearing option elements on focusing the input element via tab](https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/20066595/).",

Adding to this as a reference: Some of the entries read "partial support due to a bug" which is not consistent with the (implicit) policy.

Base automatically changed from master to main February 12, 2021 19:00
@david1234121
Copy link

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants