This is a tracking bug for any issues that show up when attempting to run Chrome Experiments in Firefox. By their nature, such bugs are obviously chrome-parity as well. My proposal is that tracking bugs for each failing Chrome Experiment should be filed, blocking this bug; and individual issues should block their respective experiment's tracking bug (if a bug affects multiple experiments, it should block the tracking bugs of all affected experiments). Note for people testing Chrome Experiments in Firefox: Some experiments contain browser checks to display an early warning if the browser found is not Chrome. Other experiments might have hacks to work better in other browsers. So, to actually test for chrome-parity, it is a good idea to set general.useragent.override to "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/184.108.40.206 Safari/525.19" while testing.
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE. If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.