Page MenuHomePhabricator

Drop IE11 / ES5 support from the Wikidata Query Service UI
Open, Needs TriagePublic

Description

As a Wikidata developer, I want there to be a clear stance on which browsers the WDQS GUI supports and doesn’t support, so that I know how to write my code.

Problem:
As far as I’m aware, the query service UI nominally still supports IE11 – I don’t think we’ve made a decision to drop it in the past. (Note that MediaWiki recently dropped ES5 support, see T178356.) That said, I don’t think it’s actually supported very well – T243382 has gone unaddressed for years, for instance, and IIRC @Michael tested it in a Windows VM more recently and found that it was totally broken. (But I’m not aware of any other user complaints about it either.)

Let’s have a proper decision from Wikidata product management about which browsers we support.

Acceptance criteria:

  • The decision about which browsers are supported is made and recorded somewhere.
  • Potentially, follow-up tasks for e.g. adjusting ESLint config are created.

Open questions:

Event Timeline

and IIRC @Michael tested it in a Windows VM more recently and found that it was totally broken.

Yup:

image.png (701×820 px, 73 KB)

The only thing that “works” is that the initial text input (to be replaced by CodeMirror) is a text area, and the “run” button is a real button, and we wrapped them in a <form>, so you can type in your query and click the button and the browser will submit it and ask if you want to download the result returned by the query service. But no part of the interactive UI works. (This is even worse than the no-JS experience, because for no-JS users we at least have a <noscript> element with a vaguely helpful message. IE11 users don’t even get that.)