PWA

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

Summary

Hi,

I ran Lighthouse from Chrome dev tools on this page.
https://ravikirans.com/az-204-azure-exam-study-guide/

Under SEO, Lighthouse suggests that "Image elements do not have [alt] attributes"
But, it doesn't point out which image element doesn't have the alt attribute.

I manually checked each imag

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

Expected results

Headers should be placed in following order:

• Item
• Description
• Size
• Colour
• Quantity
• Amount

Actual result

Headers are placed in following order:

• Item
• Description
• Colour
• Size
• Quantity
• Amount
  (Size and Colour headers do not match the data below)

Screenshots

!payment_incorrect_headers.png|width=91.66666666666666%!

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

Characters like č ć ž š đ use a fallback font instead of the original one. I believe this issue was not present in the v1. Fonts such as Lato or Montserrat definitely support accented characters, so I think this is a bug.