Usage of !important for components styling causes error on AMP pages.
See original GitHub issueI tried using this package for an AMP page and noticed that I was getting errors related to the usage of !important
in my styles. After doing some research I found out this was because the package uses !important
for some of its stylings as you can see here
Question:
- Is there any specific reason why
!important
is used in these cases? - Is there a workaround for this?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
AMP validation errors
This error occurs when you specify a layout for the AMP tag, and the layout contains a disallowed attribute. Disallowed attributes for layout...
Read more >AMP: styles missing when importing standard css files in a ...
Use withAmp on your page; View the amp version and notice standard imported css is missing. Expected behavior. Import both styled components and ......
Read more >Showing error When I add map iframe in AMP page
1 Answer 1 · An amp-iframe may not appear close to the top of the document (except for iframes that use placeholder as...
Read more >How to Use AMP(Accelerated Mobile Pages) More Efficiently?
AMP (Accelerated Mobile Pages) is a web component framework to help the developer create user-first websites. AMP is quite different from ...
Read more >How do I use Google AMP? - Blog - Marfeel
When you have resolved the validation errors and previewed the page, whereupon it looks good, it's time to add the canonical links between...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see. And I think you are right ! I’ll create a branch for you especially to test this feature. You’ll be able to install it with yarn or npm. If it is concluant and with your feedbacks, I’ll upgrade the module ! 😉 This should be done by Monday.
After testing, everything works as expected. If you want you can merge this to the master branch. Until then I will continue using my own fork.