You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2018. It is now read-only.
The show_recent_comments_widget_style filter allows this to be turned off, which it must be for AMP validity. Since it is off, the theme itself will need to incorporate this CSS rule, except for !important since this is also invalid in AMP.
Yes, there could. I think if you submit this as-is, however, AMP there will be an error displayed at that time, will it not? In this case here, the field is marked as url and so the browser is reporting it as invalid. However, WordPress on the backend will correctly prepend it with http:// so no error will ensue. We could add more error reporting via https://www.ampproject.org/docs/reference/components/amp-form#custom-validations however I think this is beyond the scope of just adding commenting support. WordPress itself doesn't provide contextual error reporting if you supply a bad URL.
The Recent Comments widget outputs the following
style
element in thehead
via\WP_Widget_Recent_Comments::recent_comments_style()
:The
show_recent_comments_widget_style
filter allows this to be turned off, which it must be for AMP validity. Since it is off, the theme itself will need to incorporate this CSS rule, except for!important
since this is also invalid in AMP.Ref. ampproject/amp-wp#864
The text was updated successfully, but these errors were encountered: