Unknown property ‘appearance’
See original GitHub issueWhile landing Bug 1326340, we had:
TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_parsable_css.js | Got error message for jar:file:///builds/slave/test/build/application/firefox/browser/omni.ja!/chrome/pdfjs/content/web/viewer.css: Unknown property ‘appearance’. Declaration dropped.
(My best guess is due #7898)
Problems to solve here:
- why browser_parsable_css.js fails us
- how to fix
- can we use browser_parsable_css.js?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
appearance - CSS: Cascading Style Sheets - MDN Web Docs
The appearance CSS property is used to control native appearance of UI controls, that are based on operating system's theme.
Read more >css error en chrome : 'Unknown property name' - Stack Overflow
I want to modify the slider but I get this error: Unknown property name. What am ...
Read more >appearance - CSS-Tricks
The appearance property is used to display an element using a platform-native styling based on the users' operating system's theme.
Read more >Unknown property 'font-display' - WordPress.org
Hi,. I am trying to fix the Ensure text remains visible during webfont load issue. I tried to add the scripts proposed by...
Read more >CSS Appearance | Can I use... Support tables for HTML5 ...
The appearance property defines how elements (particularly form controls) appear by default. By setting the value to none the default appearance can be ......
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
Try push was good and the change got r+. I’ve relanded the pdf.js update with that fix incorporated, so I think we can close this out now.
Thank you, closing.