Open dfrg opened 1 week ago
Why not put it behind a feature and make sure we run tests for that feature?
For context, I anticipate we'll want to add more OFF.Next functionality in the not too distant future and we won't want it all commented out/ignored
Per f2f, resolved that we’ll add a spec_next
feature (off by default) to capture this and any future proposed features.
We don't want to ship experimental functionality in Chrome. Resolved per #1221 to mask out the bit and re-enable later. Also ignores two tests for this.
cc @drott