Case for a Meta bug(s)? - Firefox and non webkit browser compatability issues and progress tracking


The install text currently lists browsers based on Webkit and stating “We are aware of some minor rendering and performance issues on other browsers such as Firefox.” This text doesn’t provide a link and looking at the repo issues, there isn’t a clear set of bugs or performance issues which need to be tackled to consider Firefox and other browsers supported.

It is unclear from this text if bugs are in OpenRefine or ones the Firefox community should be tackling. Would a meta issue or a label, or would this be large enough for needing to create a project for collecting the bugs which are blocking Firefox from being considered supported?

Hi and welcome @wolfgang8741 .

I have to admit that I’m not aware of what the specific issues are with using OpenRefine with Firefox and how much of an impact they have. From tracking back through some GitHub issues and PRs it looks like we encountered issues with the scatterplot facet display and that FF is not currently in the list of browsers that we test for (see Tests failing on Firefox · Issue #3837 · OpenRefine/OpenRefine · GitHub).

I’d be happy to see a way of collating FF (and other browser) specific issues in Github and maybe this would help us understand how much of a gap there is here - although how much priority should be given to getting FF “supported” is another question and given FF market share it’s previously been suggested this shouldn’t be a priority (see Having UX tests running on Firefox · Issue #3367 · OpenRefine/OpenRefine · GitHub)