Peter W
Peter W
For Atom, to make sure you've got the italics working (on, for example, comments), you can use the chrome developer inspector (since Atom uses Chromium-based [Electron](https://github.com/electron/electron)), find the CSS class...
In Atom, `=>` (equals followed by greater-than) wasn't showing the ligature that looks like a right double arrow (unicode: ⟹). In VSCode it seems to work.  You can see...
+1. Lack of this is a showstopper for me, for using the GraphQL API.
If this PR was approved 2 years ago, is there a reason it hasn't been merged?
Related: is execution time per execution or total. Would also just be cool to see an explanation for how the cost is derived.
@da2x thanks for pointing that out! I was not aware. It [looks like](https://github.com/mozilla/standards-positions/issues/79#issuecomment-378158808) they made a decision about the spec in general, knowing that they might make separate decisions for...
A lot of this was fixed by #200 and #204 See also: #240 and #336 Still to do: * improving the map interface for blind users (#201) * user testing
I don't think this is an issue for me, but let me know if you need help or anything.
I am guessing people will hit the back button anyway. Since that UI is built into the browser, I'd suggest sticking with that.
> Filters are currently hidden when users first reach the results box. Yup, that was intentional. Can you explain the user flow that showed this as confusing? When designing it,...