Is your feature request related to a problem? Please describe.

I try to execute my first GET request and get this result:

I think the first-time-user experience could get improved here.

The hint to F12 vanishes soon, and I think accessing the error message via F12 is not a

Feature request summary
I could find some reference to the use of locale in the docs, but not which locale were supported? Can I get the interface in Spanish? The reports in Thai? What parameters are supported? Is there a list of supported strings to translate?

What is the motivation or use case for changing this?
Non-English users generally are not prioritizing accessibility https:/

Is your feature request related to a problem? Please describe.
I am using QInnerLoading a lot in my app, I think it is very convenient. I have a very common use case which is not directly covered by the component: I put a short explanation text under the spinner (e.g. "checking parameters...", "saving..." etc.).

Describe the solution you'd like
A direct solution would be to add optio

What is the motivation for adding / enhancing this feature?

Write Unit tests for HTTP2 Server Push Module (you can find it on develop branch)

What are the acceptance criteria

• Unit tests for

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTR

Bug Report

Capacitor Version

💊   Capacitor Doctor  💊 

Latest Dependencies:
  @capacitor/cli: 2.2.0
  @capacitor/core: 2.2.0
  @capacitor/android: 2.2.0
  @capacitor/electron: 2.2.0
  @capacitor/ios: 2.2.0

Installed Dependencies:
  @capacitor/electron not installed
  @capacitor/cli 2.2.0
  @capacitor/core 2.2.0
  @capacitor/android 2.2.0
  @capacitor/ios 2.2.0

[su

Here is an issues with detailed description: NekR/offline-plugin#77

This hint has been around since 2018 and is documented on webhint.io (https://webhint.io/docs/user-guide/hints/hint-doctype/). However it's not enabled by default in any of webhint's configurations (likely an oversight).

We should turn this on by default and perform any necessary cleanup in the process (e.g. switching to get locations from webhint's location-aware DOM that was added after the