I am looking for documentation on Polymers unresolved attribute. Is there any? I am not able to find it. Is it still supported in Polymer-2?
As far as I know, unresolved attribute is not from Polymer, it is from the web components. This is just a CSS pseudo-class to style elements by default.
If you would like to learn more click here.
Here is document you're looking for. It's for Polymer 0.5.
https://docs-05-dot-polymer-project.appspot.com/0.5/docs/polymer/styling.html#fouc-prevention
Related
I have a project where I'm using AngularJS, but one of the requirements is that my app must pass official HTML5 and CSS3 validation.
Why are apps built with AngularJS not passing official W3C HTML5 validation? I really like AngularJS, so what should I do? Do I really have to build it from scratch or is there any reasonable article/blog which address this issue so I can explain it to my professor?
According to some other Stackoverflow QA you can pre-fix your angularjs attributes with the data- attribute.
So ng-app would become data-ng-app. This would mean that your markup is valid html5 and still work with angularjs.
See these questions for reference.
AngularJS tags attributes
Can I use another prefix instead of `ng` with angularjs?
It is very late to this answer, but I wrote a basic tool called angular-html5 which will convert directives to data-directives automatically. There are also grunt and gulp plugins to be used in build steps.
That way you can still write:
<div ng-if="whatever"></div>
And it will turn into:
<div data-ng-if="whatever"></div>
Just add it to your workflow, and you can use it similarly to using ng-min for minification.
See Angular Directives Normalization Rules for further information.
Is the <firebase-login> element available in Polymer 1.0?
The documentation here for the <firebase-element> makes no mention of the <firebase-login> element. However it does mention <firebase-auth>.
On the other hand, my Polymer Starter Kit (PSK) ships the <firebase-login> element.
Which is the correct element to use? Do I need to update my PSK?
What's going on here?
You have to use <firebase-auth>.
Github Demo
Documentation
I tried to find resources about 'alert' element, but nothing came out.
<alert type="success">Your message</alert>
But I can use it without issue. How can I apply CSS styles to different alert's type?
You look like you are trying to use Bootstrap's 'alert' classes (e.g. 'success').
http://getbootstrap.com/components/#alerts
The only way to make that a semantic element like <alert /> that I know of is something like AngularJS: http://angular-ui.github.io/bootstrap/#/alert
In this case, it is all styled by Bootstrap, or whatever Bootstrap theme you are using.
First there is not an HTML tag alert. you can create an alert with javascript.
You cannot add style to an alert as it is produced by the browser by default.
Have a look to this post:
How do I style the alert box with CSS?
W3C is always a very credible source for HTML syntax.
http://www.w3.org/TR/html-markup/Overview.html#toc
Now for where you heard about an <alert> element I have no idea. Never heard of it, but that does not mean it does not exist. W3C does not have it in this "complete set of HTML elements". It may be an element something other than HTML
As far as I know, and as some others have pointed out, there is no alert element in HTML.
However, you can use it. To allow for the HTML evolution, any modern browser will accept happily any unkown element.
I am not saying it is a good practice to use whatever name you want for an element. I am saying that the browsers will accept it.
About giving it format, use standard practices. Give it a class, or an id, and reference that in the CSS. No problem .
Technically there is a tag but its for html5 and its not completly supported,There is a table at the end of this article that shows browser compatibility.
hope this is informative:
Native Popups and Modals With the HTML5 “dialog” Element
You could use Alertify.
It has pretty decent customization options.
I have set my CSS level to 3, yet transitions are not being detected by phpStorm.
-webkit-transition
is a viable property that you can give an element. You can even check it here:
Transitions W3C
Also, I am using Level 3 of CSS3. So why does it give an error?
Is there any way to solve this?
In Webstorm 8 you can check "Ignore vendor specific CSS properties" under Project Settings -> Inspections -> CSS -> Unknown CSS Property and W3C CSS Validator in the same category. Custom properties (like transition) can be defined (comma-delimited) in Unknown CSS Property entry. This is probably applies for PhpStorm as well.
W3C CSS Validator Inspection in PhpStorm is exactly the same as what you get here (the official W3C CSS Validator website), just a local version -- nothing more.
If aforementioned official online tool produces errors/warnings on your code then there is nothing you can do about it except disabling this extra inspection (yes, this is additional inspection to PhpStorm's own inspections).
If it's opposite (online tool produces no errors or warnings) then submit a bug report to the Issue Tracker and in one of the next releases PhpStorm will have more up-to-date version of this tool.
Alternatively, you can add the unknown CSS property to custom properties, as shown in the following screenshot (this is the result after you run "Inspection Code..." action):
This is a way to train your PhpStorm/WebStorm with the missing CSS properties that you use. I also export my WebStorm/PhpStorm settings so once I fixed these missing CSS properties, i will not have to do it again.
I ran my site through the W3C validator for HTML 5, which is still experimental, I know. I got this warning with it though that I don't really understand:
The menu element is not supported by browsers yet. It would probably be better to wait for implementations.
I'm confused why this warning exists. What exactly needs to be "implemented" in the browser? As far as I was aware, the <menu> element was just another element for better semantic meaning, that was basically equivalent to a <div> element. Did I miss something? Is there something special that browsers are supposed to do with this element?
The menu tag is designed to contain 'commands' (see What exactly is the HTML5 <command> tag and what is the browser support). It is the command functionality that has not been widely implemented yet.
It may be implemented through a right-click menu, through an additional menu in the browser, or something else entirely.
Lots more good info here: http://www.html5laboratory.com/by-your-command.php