Browser support
FOLIO should run and perform well on any modern browser compliant with recent standards from W3C (e.g. HTML, CSS, DOM) and ECMA (e.g. ECMAScript [JavaScript]). We use the current desktop version of Google Chrome from the Stable channel as a 'reference implementation' for these standards. Due to time and resource constraints, we only regularly evaluate functionality and performance against our chosen reference implementation.
Browser-specific bug reports will be accepted. Although we prioritize making things work correctly in our reference implementation, we also evaluate a bug's severity and scope when setting its priority.
Comments
Going to ask steve when a DB merge will be good for him - rest should have gone in
I think it would be good for there to be advice on how to do this. I would want this with the rest of the documentation about browser support.
I wonder if we might be intending to merge our work with the existing browser support document and that will be extended with this guidance.
This looks good to me from the TC perspective. PC / Support SIG will probably have input.
It seems like some of the Rationale section from the Browser support document that @Julian Ladisch would be worth preserving/including. I think it's good to document the motivation for policies, it helps us navigate when we get into legalistic binds.
I like this. Is this the place to discuss how UI bugs are triaged in terms of teams vs stripes or does that go in some other documentation? (Or maybe it is already understood by the necessary people?)