GraphQL

The fix described in issue #20179 introduces a regression, especially from an accessibility perspective. When declaring an empty alt-attribute for an image using the keyword GATSBY_EMPTY_ALT in markdown (![GATSBY_EMPTY_ALT](rel/path.jpg) and having set showCaptions: true in the plugin-options in gatsby-config.js, the plugin produces unwanted HTML:

<figure class="gatsby-resp-i

Prettier 2.4.1
[Playground link](https://prettier.io/playground/#N4Igxg9gdgLgprEAuEAdKABAZhATgdwENcATAAgHIcIA6AZzDrorPwEsYALMgCnTLIASSAFsADtAQw6SMrjgkANOgCUAbnQhFICGJhtodZKGK4I+AArEERlIQA2RAJ5HtAI1yEwAazgwAyoQicAAybFBwyFgOdHDunj5+-mJe4QDmyDC4AK5xIHAibgokCiGEUGnZhGlwAGJ4IoQw+hXIIITZMBBaIJwwIvYA6pwccHQpYHD+NhxsAG4cTm2MriDhsbgwFp5pjVExeQBWdAAe-un2cACK2RDw+-ax2im4G20MTD1iuOEwg2wkLjIAAcAAZnmZYoNPG

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

I'm always frustrated when the keyboard navigation doesn't work on lists. Power search has an auto-complete / search suggestions list that doesn't support keyboard navigation.

To reproduce:

1. Press / from any page in Hoppscotch to bring up power search
2. Try navigating through search suggestions or auto-complete if you type in a query through the keyboard

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

Seems this is possible somehow with netlify + express + websockets?

https://github.com/Nenino2/express-netlify-websockets-example/blob/master/assets/js/app.js

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

Hello. When changing L

https://leapgraph.com/graphql-api-security

This article mentions several add-on packages that Reaction may want to use. This issue is simply to investigate whether these vulnerabilities are present and try adding the packages to solve them.

Issue Type (check one)

• Bug Report

Description (type any text below) -->

When tabbing through the Spectrum interface it's difficult to know what you're interacting with since the outlines for tabbable elements have been removed.

If you force outlines back on you can see what is being tabbed.

*:focus {
    outline: 3px solid orange !important;
    outline-offse

Focusing on the input makes the border gray, but it should stay red:

This should just be a matter of adding a :focus style in scaffold.css.

Just gave VulcanJS a try after using Meteor for a while. I'm getting the following error:

`
Warning: React.createFactory() is deprecated and will be removed in a future major release. Consider using JSX or use React.createElement() directly instead.
meteor://💻app/packages/vulcan_lib.js:422
if (error) throw error; // eslint-disable-next-line no-console
^

[Error:

Summary

Add a site AMP version.

Basic example

Nuxt.js has an example: https://github.com/nuxt/nuxt.js/tree/dev/examples/with-amp
Gatsby AMP Plugin: https://www.gatsbyjs.org/packages/gatsby-plugin-amp/

Motivation

The AMP Project support is very important to accessibility and Google's Pagerank. So, it could will be awesome had this support in Gridsome.