Hi Paulina - thanks, good to know on IE.
To go into a little more detail - our client is operating their own analytics that indicates to them that ~2% of their visitors are using IE11. Consequently they've decided they want to support IE11, and have asked us to add support.
From our perspective it would have been a lot easier if we could have found a page in Prismic's docs that explicitly states the browsers that are supported, even if it's just a relative list as browserslist supports, for example
>2%, last 2 versions (which translates to any browsers used by >2% of the population, and only the 2 most recent versions).
Armed with that information we would have simply told our client that whether IE11 works currently or not, it's not supported and therefore we should simply reject requests from IE11 to our project to preempt things breaking in the future. However the only info we could find was that IE11 wasn't supported for editing, but no info on whether content could be fetched from your API by visitors to our project using IE11.
Without that info we continued under the impression IE11 was supported and assumed the problem was in our own code, and attempted to get IE11 working. We ultimately found that your content API sends messages that IE11 can't understand and causes it to fail security checks and not load content, but this leaves our client under the impression that we should speak to you guys to discuss having IE11 support fixed.
So after all that I'm just asking if browser support could be specified in the docs - it'll save you guys any unnecessary noise from support tickets and would have saved us at least an afternoon of debugging! Apologies for plodding through the entire client interaction - sadly though this a fairly common development story.