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
It would be nice to be able to publish an official browser support matrix for the OpenTelemetry web related plugins. We could use Sauce Labs or Browser Stack to automate this testing especially of browsers like Internet Explorer, Safari and Android/iOS browsers that can be hard to test on regular CI platforms.
It would be nice to show the browser support statuses on our home page with badges similar to the Elastic RUM JS Agent GitHub page.
@mayurkale22 or @dyladan would one of you be willing to go through the Open Source project account request process with both Sauce Labs and Browser Stack for OpenTelemetry JS? That way we can try both and see which one is better.
cc/ @obecny not sure how this fits in your timeline / priorities, but I think doing this would be an important step before we can call the browser plugins "GA".
The text was updated successfully, but these errors were encountered:
@mayurkale22 or @dyladan would one of you be willing to go through the Open Source project account request process with both Sauce Labs and Browser Stack for OpenTelemetry JS? That way we can try both and see which one is better.
It would be nice to be able to publish an official browser support matrix for the OpenTelemetry web related plugins. We could use Sauce Labs or Browser Stack to automate this testing especially of browsers like Internet Explorer, Safari and Android/iOS browsers that can be hard to test on regular CI platforms.
It would be nice to show the browser support statuses on our home page with badges similar to the Elastic RUM JS Agent GitHub page.
@mayurkale22 or @dyladan would one of you be willing to go through the Open Source project account request process with both Sauce Labs and Browser Stack for OpenTelemetry JS? That way we can try both and see which one is better.
Here are relevant links:
Source project application
cc/ @obecny not sure how this fits in your timeline / priorities, but I think doing this would be an important step before we can call the browser plugins "GA".
The text was updated successfully, but these errors were encountered: