Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adapt the plugin for Firefox #5

Open
derevnjuk opened this issue Dec 3, 2019 · 8 comments
Open

Adapt the plugin for Firefox #5

derevnjuk opened this issue Dec 3, 2019 · 8 comments
Assignees
@derevnjuk
Labels
Priority: low Type: enhancement New feature or request.

Comments

@derevnjuk
Copy link
Member

derevnjuk commented Dec 3, 2019 •
edited
Loading

Cypress doesn't support Firefox yet

cypress-io/cypress#1096
https://bugzilla.mozilla.org/show_bug.cgi?id=1605512
@derevnjuk derevnjuk added Type: enhancement New feature or request. Priority: high labels Dec 3, 2019
@derevnjuk derevnjuk self-assigned this Dec 3, 2019
@derevnjuk

This comment was marked as outdated.

Sign in to view
@weo3dev
Copy link

weo3dev commented Dec 18, 2019

So the priority for use in Firefox is low? As in, not a high priority? Just wanting some clarification on this topic as I have no intention to be forced to use Chrome for any project or tool.

@bararchy
Copy link
Member

@weo3dev As noted by @ArtemDerevnjuk above comment this is currently blocked by Firefox capabilities, as you can read in #6 (comment) we are indeed working with their team on this.

The "low" priority is that this task cannot progress until fixed somewhere else.
As a user of Firefox and a lover of opensource I promise you we will do our best to allow Firefox support when it's technically possible.

We will keep this issue updated with our progress, be sure to subscribe to it if you want to get notification when this happens.

@weo3dev
Copy link

weo3dev commented Dec 18, 2019

Thank you so very much for the quickest response ever! I was reading #6 and I guess I was confused in my brain so now it makes sense the order in which development has to proceed.

Definitely subscribed to a PR tracker and an issue tracker so I can stay up to date.

Thank you again, keep up the good work!!

@derevnjuk derevnjuk pinned this issue Jan 6, 2023
@rmacklin

This comment was marked as resolved.

Sign in to view
@derevnjuk derevnjuk mentioned this issue Sep 12, 2024
Closed
@rmacklin

This comment was marked as off-topic.

Sign in to view
@derevnjuk

This comment was marked as off-topic.

Sign in to view
@rmacklin rmacklin mentioned this issue Sep 13, 2024
Merged
@rmacklin

This comment was marked as off-topic.

Sign in to view
derevnjuk pushed a commit that referenced this issue Sep 16, 2024
@rmacklin
feat(plugin): make plugin a "no-op" in unsupported browsers (#460)
3592682 
Previously the plugin would throw an error when it was running in an
unsupported browser. This was not great for plugin consumers who run
their cypress tests in both supported and unsupported browsers and are
fine with only having HAR recording in supported browsers: It forced
them to conditionally enable this plugin.

To address this, we're changing the plugin to do nothing except `warn`
that HAR recording is not supported when running in an unsupported
browser.

relates-to: #5 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@derevnjuk derevnjuk

Labels
Priority: low Type: enhancement New feature or request.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bararchy @rmacklin @weo3dev @derevnjuk