Submitting new feature data sets #2

Closed
skddc opened this Issue Apr 9, 2012 · 5 comments

2 participants

@skddc

Hi,

I tried to get to this in an html5please issue discussion, but it was a bit off-topic there:

  • How do I go about submitting new feature data?
  • If it's not possible via pull requests, why not?

Thanks,
Sebastian

@Fyrd
Owner

There's currently no official way to submit data, the rare times people have sent it to me it's mostly just been in emails, etc.

I'll be happy to consider data submitted via pull requests, though I won't be able to automatically import it from there (currently) since the JSON file itself is exported from the caniuse database. So for now I would simply read the data and add it manually, though if it becomes popular I could automate that.

Additionally, I would recommend you'd also submit one or more tests to detect the feature, which would be necessary to update the data on new browser releases.

@skddc

What should be the format of those tests?

@Fyrd
Owner

Just wrote some documentation on that here:
http://tests.caniuse.com/submit.html

Let me know if you need any further details.

@skddc

Thanks, will look into it.

@Fyrd
Owner

The main issue here was of course made possible recently, so closing the issue.

@Fyrd Fyrd closed this Oct 16, 2012
@hakanson hakanson added a commit to hakanson/caniuse that referenced this issue Sep 8, 2014
@hakanson hakanson changed "d" to "n d #2" under firefox ab643a1
@zack-lin zack-lin added a commit to zack-lin/caniuse that referenced this issue May 14, 2015
@zack-lin zack-lin Update contentsecuritypolicy.json
Test on UCBrowser, make sure it uses #2, Supported through the `X-Webkit-CSP` header
c69c1a5
@myakura myakura added a commit to myakura/caniuse that referenced this issue Sep 25, 2015
@myakura myakura update text-align-last support table
* update Chrome as it will be enabled by default in Chrome 47
  https://chromium.googlesource.com/chromium/src/+/87ca955695
* remove IE notes from Edge
* add more Android Chrome support status
  (marked it as "n d #2" as there hasn't been public CrMo 47 build yet)
9882d54
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 7, 2016
@PascalReintjens PascalReintjens push-api.json: add note #2 to Opera Mobile 37
Adds note #2 ("Requires browser to be running to receive messages") to Opera Mobile 37
d29dabe
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 12, 2016
@PascalReintjens PascalReintjens Update push-api - Remove #2 on Opera Mobile
Since the merged pullrequest #2635 removed #2 on Chrome for Android, this means that Opera for Android 37 shouldn't have this note too, because it behaves exactly the same. Both need their app to be running but not necessarily visible for the user - they are both using a background service.
4727e19
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 12, 2016
@PascalReintjens PascalReintjens Update push-api - Make meaning of #2 clearer
Note #2 wasn't really clear in which cases it applyed. You could argue that running means the full visible browser or running allready means a background-service.
6e8c0d4
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 12, 2016
@PascalReintjens PascalReintjens Update push-api - Remove #2 on Opera Mobile
Since the merged pull request #2635 removed #2 on Chrome for Android, this means that Opera for Android 37 shouldn't have this note too, because it behaves exactly the same. Both need their app to be running but not necessarily visible for the user - they are both using a background service.
2da1914
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 12, 2016
@PascalReintjens PascalReintjens Update push-api - Make meaning of note #2 clearer
Note #2 wasn't really clear in which cases it applied. You could argue that running means the full visible browser or running already means a background-service.
60e905c
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 13, 2016
@PascalReintjens PascalReintjens Update push-api - Remove #2 on Opera Mobile
Since the merged pull request #2635 removed #2 on Chrome for Android, this means that Opera for Android 37 shouldn't have this note too, because it behaves exactly the same. Both need their app to be running but not necessarily visible for the user - they are both using a background service.
9dd2cbf
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 13, 2016
@PascalReintjens PascalReintjens Update push-api - Make meaning of note #2 clearer
Note #2 wasn't really clear in which cases it applied. You could argue that running means the full visible browser or running already means a background-service.
18833e9
@PascalReintjens PascalReintjens added a commit to PascalReintjens/caniuse that referenced this issue Jul 13, 2016
@PascalReintjens PascalReintjens Update push-api - Make meaning of note #2 clearer
Note #2 wasn't really clear in which cases it applied. You could argue that running means the full visible browser or running already means a background-service.
9152939
@miguelao miguelao pushed a commit to miguelao/caniuse that referenced this issue Aug 24, 2016
@NOtherDev NOtherDev #2 Clarification for Pointer Device Adaptation, #3 more info on Point…
…er Events API
1cbe4cc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment