I just installed Angular Material to my new project and noticed that it throws over a hundred warnings in the Firefox console, mostly dropped declarations. Besided this, no errors at all. I tried this with a local file and a CDN link and the result is the same. Does anybody know what causes this and how to fix it?
It's for you so you can avoid using those declaration as they have planned to implement the new or changed name. I got those warning all the time and it means as long i stick to the same version i could forget about those warnings but if i upgrade i can be in trouble.
Related
I am using include-media in a project and getting the syntax error
[scss] ) expected
when viewing this mixin in my vscode editor. I have had a look at this question, but it is not about the same syntax I am experiencing.
Here is a screenshot of the section with a problem in this file
I have not made not made any changes to this mixin, I simply downloaded and included it in the project it as outlined here
Questions:
What is causing this error?
How come I am still able to use this mixin even though it has an error?
How can I solve this?
1. What is causing this error?
This issue is occuring because vscode editor does not support css preprocessors completely.
2. How come I am still able to use this mixin even though it has an error?
You will get your output as the include-media scss is completely fine.
3. How can I solve this?
You need to add vscode service for css which will help to detect css pre-processors syntax and your error will be resolved. Include this vscode script in your vscode editor. As mention here.
https://github.com/Microsoft/vscode-css-languageservice
Thanks
Enviroment
I have an extjs 6 application which is already compiled and the css files like they should be. This application wasn't compiled for a while and now it's generating a different (wrong) css file. Since someone else changed the app, I have no clue what has changed since the last compilation. I compile with sencha app build development and the following CSS files change:
build\development\MyApp\classic\resources\MyApp-all_1.css
build\development\MyApp\classic\resources\MyApp-all_2.css
There are a few more files in the folder which do not change.
Versions:
Sencha Cmd 6.1.3.42
SDK Version (if neccessary) 6.0.2.407
Problem
I want to generate the same css like before. It seems there are just a few files which are not included within the compilation process, like:
ext/classic/theme-base/sass/etc/mixins/frame.scss
ext/classic/theme-base/sass/etc/mixins/slicer.scss
ext/classic/theme-neutral/sass/src/tab/Tab.scss
Question
What do I have to do, to get the old css? Is there some file with includes? Like classic\sass\src\view\main\Main.scss or something? I guess those includes are somewhere (since it already worked at least once) and maybe commented out or something.
What I've already tried
I tried to compile with different themes refered by the app.json attribute was builds->theme. I also tried a lot of playing around stuff, which I can't describe here in detail.
Any advice would be greatly appreciated!
Thanks in advance!
If you have any questions leave a comment and I'll try to add it to my text!
I am getting really confused about configuring Sass config options. Basically I want to disable the line comments in the compiled css file. So I went in and created a sass.rb in the Initializers folder with the following line:
Rails.application.config.sass.line_comments = true
I then restart my apache server and check in Safari web developer, my css file still contains the comments like /* line## /path/to/css/file */ above every css statement. I then test it in Firefox and open Firebug, and I don't see those line comments there, which suggest inconsistent browser behavior.
So I go back to my initializer sass.rb file and turn on line_comments, restart the web server and try again, this time I get the exact same result as before, nothing's changed, that basically tells me either that's specific to the browsers, there's a problem with the setting scope/syntax, or there's a caching issue (I'm working in development, so there shouldn't be any caching, right?). I'd really appreciate if someone can provide some insight on this. Thanks.
EDIT: The proposed solution to make a change to the sass file(s) didn't solve anything so I doubt it is the same problem.
Note: I am using sass with rails and I am getting separate css files for each of my sass files, which doesn't seem very right...
The problem was a combination of needing to set config.assets.debug to false for development, setting config.assets.compress to true, and probably a better understanding of sass compilation.
I use SASS to preprocess my CSS within Netbeans on Ubuntu. If I generate the CSS without minifying, I don't get any errors at all. However, I want to make the CSS minified, so I've added the --compass --style compressed options to the SASS command.
When SASS generates a minified .css file, Netbeans marks it with all sorts of errors. Mainly they say Unexpected token RBRACE found, Unexpected token NL found, Disable filtering of "Unexpected token IMPORTANT_SYM found" CSS parsing error, and Premature end of file.
Despite searching the net, I can't determine if these are errors or warnings that I should take seriously, let alone how to get rid of them. My web pages still seem to render with the right styles, so maybe it's just warnings from Netbeans.
If they're just warnings that don't affect anything, how do I get rid of them? If they are actual errors, why is the SASS preprocessor generating them?
Starting with NetBeans 7.4 (with all updates), if you click on the bulb icon on line with error, there is option to filter out all css errors in given file/folder/parent folder/project etc. or specific type of error. On your first screenshot, there is such option (not sure why it is missing option to filter all css errors though)
I am completely stumped right now. I am working on an AIR application, everything was working perfectly, I did some small changes to code (completely unrelated to fonts, components or anything of this kind) when suddenly, during testing, I am flooded with hundreds of warning: incompatible embedded font errors. I didn't change any project settings, didn't make any framework update, I tried Clean and restating Flash Builder.
Now, I am working on a project which uses modules and both MX (only Datagrid) and Spark components, so I am using two versions of font:
#font-face {
src:url("/assets/font/helvetica.otf");
fontFamily: "Helvetica";
embedAsCFF: true;
}
[...]
[Embed(source="../assets/font/helvetica_3.otf", fontFamily="Helvetica_2",
embedAsCFF="false", mimeType="application/x-font")]
private var _font_:Class;
As you can guess, Helvetica is for Spark components while the other one is for MX. Two curious errors:
warning: incompatible embedded font 'Helvetica' specified for spark.components::Label (countdown) . This component requires that the embedded font be declared with embedAsCff=true Isn't it already?
warning: incompatible embedded font 'Helvetica_2' specified for mx.controls.dataGridClasses::DataGridItemRenderer (DataGridItemRenderer501) . This component requires that the embedded font be declared with embedAsCff=false. Isn't it already too?!
These errors relate to MODULES which I import into the project (yes, my own). Text in the main air app works more or less fine (Diacritic characters are not displayed anymore). I am using additionally these command line parameters:
-isolate-styles=false (So skins and ANYTHING is actually applied to the modules, without it there are no errors, but modules have no styles)
-keep-all-type-selectors=true (Removing this doesn't help anyway)
Anyone had similar problem and managed to find the cause? I tried to undo last changes I made but without avail...
Update:
Well, weird enough I found the source of problem. In one of the module's components I imported class which is also imported by Main app, which resulted in problem. The funny thing is, it worked fine until I cloned the component to make a similar one, which isn't even imported to ANY of the modules yet. Once again Flex proved it's weirdness.