pkg/polymer/lib/src/build/generated/messages.html - Issue 543963002: Link to stable-errors site from pub-build messages on the command line.

Unified Diff: pkg/polymer/lib/src/build/generated/messages.html

Issue 543963002: Link to stable-errors site from pub-build messages on the command line. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Patch Set: Created 6 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: pkg/polymer/lib/src/build/generated/messages.html

diff --git a/pkg/polymer/lib/src/build/generated/messages.html b/pkg/polymer/lib/src/build/generated/messages.html

index bcb5c6d6f8a1881dc7c8c76849196197fcdf048c..61089c9dfca143c6089c2988b2a316da8bb6e61b 100644

--- a/pkg/polymer/lib/src/build/generated/messages.html

+++ b/pkg/polymer/lib/src/build/generated/messages.html

@@ -35,7 +35,7 @@ body {

font-family: Roboto, sans-serif;

}

-h1 {

+h2 {

font-family: Montserrat, sans-serif;

box-sizing: border-box;

color: rgb(72, 72, 72);

@@ -45,7 +45,7 @@ h1 {

font-weight: normal;

}

-h2 {

+h3 {

font-family: Montserrat, sans-serif;

box-sizing: border-box;

color: rgb(72, 72, 72);

@@ -59,7 +59,6 @@ pre {

display: block;

padding: 9.5px;

margin: 0 0 10px;

- line-height: 1.42857143;

color: #333;

word-break: break-all;

word-wrap: break-word;

@@ -79,33 +78,35 @@ code {

background-color: #f9f2f4;

}

-pre > code {

+pre code {

white-space: inherit;

+ color: inherit;

+ background-color: inherit;

}

a {

color: rgb(42, 100, 150);

}

-h2 > a {

+h3 > a {

display: none;

font-size: 0.8em;

}

-h2:hover > a {

+h3:hover > a {

display: inline;

}

</style>

<body>

-<h1>Messages from package <code>code_transformers</code></h1>

+<h2>Messages from package <code>code_transformers</code></h2>

<hr />

-<h2 id="msg_code_transformers_1">Absolute paths not allowed <a href="#msg_code_transformers_1">#1</a> {#hashTag}</h2>

+<h3 id="code_transformers_1">Absolute paths not allowed <a href="#code_transformers_1">#1</a></h3>

<p>The transformers processing your code were trying to resolve a URL and identify

a file that they correspond to. Currently only relative paths can be resolved.</p>

<hr />

-<h2 id="msg_code_transformers_2">Invalid URL to reach another package <a href="#msg_code_transformers_2">#2</a> {#hashTag}</h2>

+<h3 id="code_transformers_2">Invalid URL to reach another package <a href="#code_transformers_2">#2</a></h3>

<p>To reach an asset that belongs to another package, use <code>package:</code> URLs in

Dart code, but in any other language (like HTML or CSS) use relative URLs.</p>

<p>These are the rules you must follow to write URLs that refer to files in other

@@ -217,7 +218,7 @@ existing transformers do not fix URLs, they just detect inconsistencies and

produce an error message like this one, instead.</p></li></ul>

<hr />

-<h2 id="msg_code_transformers_3">Incomplete URL to asset in another package <a href="#msg_code_transformers_3">#3</a> {#hashTag}</h2>

+<h3 id="code_transformers_3">Incomplete URL to asset in another package <a href="#code_transformers_3">#3</a></h3>

<p>URLs that refer to assets in other packages need to explicitly mention the

<code>packages/</code> directory. In the future this requirement might be removed, but for

now you must use a canonical URL form for it.</p>

@@ -225,86 +226,86 @@ now you must use a canonical URL form for it.</p>

you might expect a.html to import <code>../b/b.html</code>. Instead, it must import

<code>../../packages/b/b.html</code>.

See <a href="http://dartbug.com/15797">issue 15797</a>.</p>

-<hr /><h1>Messages from package <code>observe</code></h1>

+<hr /><h2>Messages from package <code>observe</code></h2>

<hr />

-<h2 id="msg_observe_1"><code>@observable</code> not supported on libraries <a href="#msg_observe_1">#1</a> {#hashTag}</h2>

+<h3 id="observe_1"><code>@observable</code> not supported on libraries <a href="#observe_1">#1</a></h3>

<p>Only instance fields on <code>Observable</code> classes can be observable,

and you must explicitly annotate each observable field as <code>@observable</code>.</p>

<p>Support for using the <code>@observable</code> annotation in libraries, classes, and

elsewhere is deprecated.</p>

<hr />

-<h2 id="msg_observe_2"><code>@observable</code> not supported on top-level fields <a href="#msg_observe_2">#2</a> {#hashTag}</h2>

+<h3 id="observe_2"><code>@observable</code> not supported on top-level fields <a href="#observe_2">#2</a></h3>

<p>Only instance fields on <code>Observable</code> classes can be observable,

and you must explicitly annotate each observable field as <code>@observable</code>.</p>

<p>Support for using the <code>@observable</code> annotation in libraries, classes, and

elsewhere is deprecated.</p>

<hr />

-<h2 id="msg_observe_3"><code>@observable</code> not supported on classes <a href="#msg_observe_3">#3</a> {#hashTag}</h2>

+<h3 id="observe_3"><code>@observable</code> not supported on classes <a href="#observe_3">#3</a></h3>

<p>Only instance fields on <code>Observable</code> classes can be observable,

and you must explicitly annotate each observable field as <code>@observable</code>.</p>

<p>Support for using the <code>@observable</code> annotation in libraries, classes, and

elsewhere is deprecated.</p>

<hr />

-<h2 id="msg_observe_4"><code>@observable</code> not supported on static fields <a href="#msg_observe_4">#4</a> {#hashTag}</h2>

+<h3 id="observe_4"><code>@observable</code> not supported on static fields <a href="#observe_4">#4</a></h3>

<p>Only instance fields on <code>Observable</code> classes can be observable,

and you must explicitly annotate each observable field as <code>@observable</code>.</p>

<p>Support for using the <code>@observable</code> annotation in libraries, classes, and

elsewhere is deprecated.</p>

<hr />

-<h2 id="msg_observe_5"><code>@observable</code> field not in an <code>Observable</code> class <a href="#msg_observe_5">#5</a> {#hashTag}</h2>

+<h3 id="observe_5"><code>@observable</code> field not in an <code>Observable</code> class <a href="#observe_5">#5</a></h3>

<p>Only instance fields on <code>Observable</code> classes can be observable,

and you must explicitly annotate each observable field as <code>@observable</code>.</p>

<p>Support for using the <code>@observable</code> annotation in libraries, classes, and

elsewhere is deprecated.</p>

-<hr /><h1>Messages from package <code>polymer</code></h1>

+<hr /><h2>Messages from package <code>polymer</code></h2>

<hr />

-<h2 id="msg_polymer_1">Import not found <a href="#msg_polymer_1">#1</a> {#hashTag}</h2>

+<h3 id="polymer_1">Import not found <a href="#polymer_1">#1</a></h3>

<p>An HTML import seems to be broken. This could be because the file doesn't exist

or because the link URL is incorrect.</p>

<hr />

-<h2 id="msg_polymer_2">Duplicate definition <a href="#msg_polymer_2">#2</a> {#hashTag}</h2>

+<h3 id="polymer_2">Duplicate definition <a href="#polymer_2">#2</a></h3>

<p>Custom element names are global and can only be defined once. Some common

reasons why you might get two definitions:</p><ul><li>Two different elements are declared with the same name.</li><li>

<p>A single HTML file defining an element, has been imported using two different

URLs.</p></li></ul>

<hr />

-<h2 id="msg_polymer_3">Missing import to polymer.html <a href="#msg_polymer_3">#3</a> {#hashTag}</h2>

+<h3 id="polymer_3">Missing import to polymer.html <a href="#polymer_3">#3</a></h3>

<p>Starting with polymer 0.11.0, each file that uses the definition

of polymer-element must import it either directly or transitively.</p>

<hr />

-<h2 id="msg_polymer_4">Invalid import inside <polymer-element> <a href="#msg_polymer_4">#4</a> {#hashTag}</h2>

+<h3 id="polymer_4">Invalid import inside <polymer-element> <a href="#polymer_4">#4</a></h3>

<p>HTML imports are expected at the top of each document, outside of any

polymer-element definitions. The polymer build process combines all your HTML

files together so you can deploy a single HTML file with your application. This

build process ignores imports that appear to be in the wrong location.</p>

<hr />

-<h2 id="msg_polymer_5">Missing call to <code>initPolymer()</code> <a href="#msg_polymer_5">#5</a> {#hashTag}</h2>

+<h3 id="polymer_5">Missing call to <code>initPolymer()</code> <a href="#polymer_5">#5</a></h3>

<p>Your application entry point didn't have any Dart script tags, so it's missing

some initialization needed for polymer.dart.</p>

<hr />

-<h2 id="msg_polymer_6">Script tags with experimental bootstrap <a href="#msg_polymer_6">#6</a> {#hashTag}</h2>

+<h3 id="polymer_6">Script tags with experimental bootstrap <a href="#polymer_6">#6</a></h3>

<p>This experimental feature is no longer supported.</p>

<hr />

-<h2 id="msg_polymer_7">Multiple Dart script tags per document <a href="#msg_polymer_7">#7</a> {#hashTag}</h2>

+<h3 id="polymer_7">Multiple Dart script tags per document <a href="#polymer_7">#7</a></h3>

<p>Dartium currently allows only one script tag per document. Any

additional script tags might be ignored or result in an error. This will

likely change in the future, but for now, combine the script tags together into

a single Dart library.</p>

<hr />

-<h2 id="msg_polymer_8">Imports before script tags <a href="#msg_polymer_8">#8</a> {#hashTag}</h2>

+<h3 id="polymer_8">Imports before script tags <a href="#polymer_8">#8</a></h3>

<p>It is good practice to put all your HTML imports at the beginning of the

document, above any Dart script tags. Today, the execution of Dart script tags

is not synchronous in Dartium, so the difference is not noticeable. However,

@@ -314,17 +315,17 @@ respect to script tags will be important. Following the practice of putting

imports first protects your app from a future breaking change in this respect.</p>

<hr />

-<h2 id="msg_polymer_9">Missing href on a <code><link></code> tag <a href="#msg_polymer_9">#9</a> {#hashTag}</h2>

+<h3 id="polymer_9">Missing href on a <code><link></code> tag <a href="#polymer_9">#9</a></h3>

<p>All <code><link></code> tags should have a valid URL to a resource.</p>

<hr />

-<h2 id="msg_polymer_10"><code><element></code> is deprecated <a href="#msg_polymer_10">#10</a> {#hashTag}</h2>

+<h3 id="polymer_10"><code><element></code> is deprecated <a href="#polymer_10">#10</a></h3>

<p>Long ago <code><polymer-element></code> used to be called <code><element></code>. You probably ran

into this error if you were migrating code that was written on a very early

version of polymer.</p>

<hr />

-<h2 id="msg_polymer_11">Definition of a custom element not found <a href="#msg_polymer_11">#11</a> {#hashTag}</h2>

+<h3 id="polymer_11">Definition of a custom element not found <a href="#polymer_11">#11</a></h3>

<p>The polymer build was not able to find the definition of a custom element. This

can happen if an element is defined with a <code><polymer-element></code> tag, but you are

missing an HTML import or the import link is incorrect.</p>

@@ -333,26 +334,26 @@ programatically using <code>document.registerElement</code>. In that case the po

will not be able to see the definition and will produce this warning.</p>

<hr />

-<h2 id="msg_polymer_12">Empty script tag <a href="#msg_polymer_12">#12</a> {#hashTag}</h2>

+<h3 id="polymer_12">Empty script tag <a href="#polymer_12">#12</a></h3>

<p>Script tags should either have a <code>src</code> attribute or a non-empty body.</p>

<hr />

-<h2 id="msg_polymer_13">Expected Dart mime-type <a href="#msg_polymer_13">#13</a> {#hashTag}</h2>

+<h3 id="polymer_13">Expected Dart mime-type <a href="#polymer_13">#13</a></h3>

<p>You seem to have a <code>.dart</code> extension on a script tag, but the mime-type

doesn't match <code>application/dart</code>.</p>

<hr />

-<h2 id="msg_polymer_14">Expected Dart file extension <a href="#msg_polymer_14">#14</a> {#hashTag}</h2>

+<h3 id="polymer_14">Expected Dart file extension <a href="#polymer_14">#14</a></h3>

<p>You are using the <code>application/dart</code> mime-type on a script tag, so

the URL to the script source URL should have a <code>.dart</code> extension.</p>

<hr />

-<h2 id="msg_polymer_15">Script with both src and inline text <a href="#msg_polymer_15">#15</a> {#hashTag}</h2>

+<h3 id="polymer_15">Script with both src and inline text <a href="#polymer_15">#15</a></h3>

<p>You have a script tag that includes both a <code>src</code> attribute and inline script

text. You must choose one or the other.</p>

<hr />

-<h2 id="msg_polymer_16">Incorrect instantiation: missing base tag in instantiation <a href="#msg_polymer_16">#16</a> {#hashTag}</h2>

+<h3 id="polymer_16">Incorrect instantiation: missing base tag in instantiation <a href="#polymer_16">#16</a></h3>

<p>When you declare that a custom element extends from a base tag, for example:</p>

</code></pre>

@@ -374,7 +375,7 @@ have the extra functionality of your custom element. In the example above, using

doing the upgrade.</p>

<hr />

-<h2 id="msg_polymer_17">Incorrect instantiation: extra <code>is</code> attribute or missing <code>extends</code> in declaration <a href="#msg_polymer_17">#17</a> {#hashTag}</h2>

+<h3 id="polymer_17">Incorrect instantiation: extra <code>is</code> attribute or missing <code>extends</code> in declaration <a href="#polymer_17">#17</a></h3>

<p>Creating a custom element using the syntax:</p>

</code></pre>

@@ -390,7 +391,7 @@ case the fix is to change the instantiation to:</p>

</code></pre>

<hr />

-<h2 id="msg_polymer_18">Incorrect instantiation: base tag seems wrong <a href="#msg_polymer_18">#18</a> {#hashTag}</h2>

+<h3 id="polymer_18">Incorrect instantiation: base tag seems wrong <a href="#polymer_18">#18</a></h3>

<p>It seems you have a declaration like:</p>

</code></pre>

@@ -406,7 +407,7 @@ either the instantiation needs to be fixed to be more like:</p>

</code></pre>

<hr />

-<h2 id="msg_polymer_19">No dashes allowed in custom attributes <a href="#msg_polymer_19">#19</a> {#hashTag}</h2>

+<h3 id="polymer_19">No dashes allowed in custom attributes <a href="#polymer_19">#19</a></h3>

<p>Polymer used to recognize attributes with dashes like <code>my-name</code> and convert them

to match properties where dashes were removed, and words follow the camelCase

style (for example <code>myName</code>). This feature is no longer available. Now simply

@@ -416,7 +417,7 @@ your property entirely in lowercase. Just be sure that your custom-elements

don't declare two properties with the same name but different capitalization.</p>

<hr />

-<h2 id="msg_polymer_20">Event handlers not supported here <a href="#msg_polymer_20">#20</a> {#hashTag}</h2>

+<h3 id="polymer_20">Event handlers not supported here <a href="#polymer_20">#20</a></h3>

<p>Bindings of the form <code>{{ }}</code> are supported inside <code><template></code> nodes, even outside

of <code><polymer-element></code> declarations. However, those bindings only support binding

values into the content of a node or an attribute.</p>

@@ -425,13 +426,13 @@ of polymer elements, so they are only supported inside <code><polymer-element

definitions.</p>

<hr />

-<h2 id="msg_polymer_21">No expressions allowed in event handler bindings <a href="#msg_polymer_21">#21</a> {#hashTag}</h2>

+<h3 id="polymer_21">No expressions allowed in event handler bindings <a href="#polymer_21">#21</a></h3>

<p>Unlike data bindings, event handler bindings of the form <code>on-click="{{method}}"</code>

are not evaluated as expressions. They are meant to just contain a simple name

that resolves to a method in your polymer element's class definition.</p>

<hr />

-<h2 id="msg_polymer_22">Nested polymer element definitions not allowed <a href="#msg_polymer_22">#22</a> {#hashTag}</h2>

+<h3 id="polymer_22">Nested polymer element definitions not allowed <a href="#polymer_22">#22</a></h3>

<p>Because custom element names are global, there is no need to have a

<code><polymer-element></code> definition nested within a <code><polymer-element></code>. If you have

a definition inside another, move the second definition out.</p>

@@ -439,34 +440,34 @@ a definition inside another, move the second definition out.</p>

You should be able to move the import out of the element definition.</p>

<hr />

-<h2 id="msg_polymer_23">Polymer element definitions without a name <a href="#msg_polymer_23">#23</a> {#hashTag}</h2>

+<h3 id="polymer_23">Polymer element definitions without a name <a href="#polymer_23">#23</a></h3>

<p>Polymer element definitions must have a name. You can include a name by using

the <code>name</code> attribute in <code><polymer-element></code> for example:</p>

</code></pre>

<hr />

-<h2 id="msg_polymer_24">Custom element name missing a dash <a href="#msg_polymer_24">#24</a> {#hashTag}</h2>

+<h3 id="polymer_24">Custom element name missing a dash <a href="#polymer_24">#24</a></h3>

<p>Custom element names must have a dash (<code>-</code>) and can't be any of the following

reserved names:</p><ul><li><code>annotation-xml</code></li><li><code>color-profile</code></li><li><code>font-face</code></li><li><code>font-face-src</code></li><li><code>font-face-uri</code></li><li><code>font-face-format</code></li><li><code>font-face-name</code></li><li><code>missing-glyph</code></li></ul>

<hr />

-<h2 id="msg_polymer_25">Error while inlining an import <a href="#msg_polymer_25">#25</a> {#hashTag}</h2>

+<h3 id="polymer_25">Error while inlining an import <a href="#polymer_25">#25</a></h3>

<p>An error occurred while inlining an import in the polymer build. This is often

the result of a broken HTML import.</p>

<hr />

-<h2 id="msg_polymer_26">Error while inlining a stylesheet <a href="#msg_polymer_26">#26</a> {#hashTag}</h2>

+<h3 id="polymer_26">Error while inlining a stylesheet <a href="#polymer_26">#26</a></h3>

<p>An error occurred while inlining a stylesheet in the polymer build. This is

often the result of a broken URL in a <code><link rel="stylesheet" href="..."></code>.</p>

<hr />

-<h2 id="msg_polymer_27">URL to a script file might be incorrect <a href="#msg_polymer_27">#27</a> {#hashTag}</h2>

+<h3 id="polymer_27">URL to a script file might be incorrect <a href="#polymer_27">#27</a></h3>

<p>An error occurred trying to read a script tag on a given URL. This is often the

result of a broken URL in a <code><script src="..."></code>.</p>

<hr />

-<h2 id="msg_polymer_28">Attribute missing "_" prefix <a href="#msg_polymer_28">#28</a> {#hashTag}</h2>

+<h3 id="polymer_28">Attribute missing "_" prefix <a href="#polymer_28">#28</a></h3>

<p>Not all browsers support bindings to certain attributes, especially URL

attributes. Some browsers might sanitize attributes and result in an

incorrect value. For this reason polymer provides a special set of attributes

@@ -481,7 +482,7 @@ For example, instead of writing:</p>

<p>For more information, see <a href="http://goo.gl/5av8cU">http://goo.gl/5av8cU</a>.</p>

<hr />

-<h2 id="msg_polymer_29">Attribute with extra "_" prefix <a href="#msg_polymer_29">#29</a> {#hashTag}</h2>

+<h3 id="polymer_29">Attribute with extra "_" prefix <a href="#polymer_29">#29</a></h3>

<p>A special attribute exists to support bindings on URL attributes. For example,

this correctly binds the <code>src</code> attribute in an image:</p>

@@ -490,42 +491,42 @@ this correctly binds the <code>src</code> attribute in an image:</p>

just have a URL, use the normal <code>src</code> attribute instead.</p>

<hr />

-<h2 id="msg_polymer_30">Internal error: don't know how to include a URL <a href="#msg_polymer_30">#30</a> {#hashTag}</h2>

+<h3 id="polymer_30">Internal error: don't know how to include a URL <a href="#polymer_30">#30</a></h3>

<p>Sorry, you just ran into a bug in the polymer transformer code. Please file a

bug at <a href="http://dartbug.com/new">http://dartbug.com/new</a> including, if possible, some example code that

can help the team reproduce the issue.</p>

<hr />

-<h2 id="msg_polymer_31">Internal error: phases run out of order <a href="#msg_polymer_31">#31</a> {#hashTag}</h2>

+<h3 id="polymer_31">Internal error: phases run out of order <a href="#polymer_31">#31</a></h3>

<p>Sorry, you just ran into a bug in the polymer transformer code. Please file a

bug at <a href="http://dartbug.com/new">http://dartbug.com/new</a> including, if possible, some example code that

can help the team reproduce the issue.</p>

<hr />

-<h2 id="msg_polymer_32"><code>@CustomTag</code> used on a private class <a href="#msg_polymer_32">#32</a> {#hashTag}</h2>

+<h3 id="polymer_32"><code>@CustomTag</code> used on a private class <a href="#polymer_32">#32</a></h3>

<p>The <code>@CustomTag</code> annotation is currently only supported on public classes. If

you need to register a custom element whose implementation is a private class

(that is, a class whose name starts with <code>_</code>), you can still do so by invoking

<code>Polymer.register</code> within a public method marked with <code>@initMethod</code>.</p>

<hr />

-<h2 id="msg_polymer_33"><code>@initMethod</code> is on a private function <a href="#msg_polymer_33">#33</a> {#hashTag}</h2>

+<h3 id="polymer_33"><code>@initMethod</code> is on a private function <a href="#polymer_33">#33</a></h3>

<p>The <code>@initMethod</code> annotation is currently only supported on public top-level

functions.</p>

<hr />

-<h2 id="msg_polymer_34">Missing argument in annotation <a href="#msg_polymer_34">#34</a> {#hashTag}</h2>

+<h3 id="polymer_34">Missing argument in annotation <a href="#polymer_34">#34</a></h3>

<p>The annotation expects one argument, but the argument was not provided.</p>

<hr />

-<h2 id="msg_polymer_35">Invalid argument in annotation <a href="#msg_polymer_35">#35</a> {#hashTag}</h2>

+<h3 id="polymer_35">Invalid argument in annotation <a href="#polymer_35">#35</a></h3>

<p>The polymer transformer was not able to extract a constant value for the

annotation argument. This can happen if your code is currently in a state that

can't be analyzed (for example, it has parse errors) or if the expression passed

as an argument is invalid (for example, it is not a compile-time constant).</p>

<hr />

-<h2 id="msg_polymer_36">No polymer initializers found <a href="#msg_polymer_36">#36</a> {#hashTag}</h2>

+<h3 id="polymer_36">No polymer initializers found <a href="#polymer_36">#36</a></h3>

<p>No polymer initializers were found. Make sure to either

annotate your polymer elements with @CustomTag or include a

top level method annotated with @initMethod that registers your

@@ -533,7 +534,7 @@ elements. Both annotations are defined in the polymer library (

package:polymer/polymer.dart).</p>

<hr />

-<h2 id="msg_polymer_37">Event bindings with @ are no longer supported <a href="#msg_polymer_37">#37</a> {#hashTag}</h2>

+<h3 id="polymer_37">Event bindings with @ are no longer supported <a href="#polymer_37">#37</a></h3>

<p>For a while there was an undocumented feature that allowed users to include

expressions in event bindings using the <code>@</code> prefix, for example:</p>

@@ -542,7 +543,7 @@ expressions in event bindings using the <code>@</code> prefix, for example:</p>

<p>This feature is no longer supported.</p>

<hr />

-<h2 id="msg_polymer_38">Private symbol in event handler <a href="#msg_polymer_38">#38</a> {#hashTag}</h2>

+<h3 id="polymer_38">Private symbol in event handler <a href="#polymer_38">#38</a></h3>

<p>Currently private members can't be used in event handler bindings. So you can't

write:</p>

@@ -551,20 +552,20 @@ write:</p>

your event handlers public.</p>

<hr />

-<h2 id="msg_polymer_39">Private symbol in binding expression <a href="#msg_polymer_39">#39</a> {#hashTag}</h2>

+<h3 id="polymer_39">Private symbol in binding expression <a href="#polymer_39">#39</a></h3>

<p>Private members can't be used in binding expressions. For example, you can't

write:</p>

</code></pre>

<hr />

-<h2 id="msg_polymer_40">A warning was found while parsing the HTML document <a href="#msg_polymer_40">#40</a> {#hashTag}</h2>

+<h3 id="polymer_40">A warning was found while parsing the HTML document <a href="#polymer_40">#40</a></h3>

<p>The polymer transformer uses a parser that implements the HTML5 spec

(<code>html5lib</code>). This message reports a

warning that the parser detected.</p>

<hr />

-<h2 id="msg_polymer_41">Possible flash of unstyled content <a href="#msg_polymer_41">#41</a> {#hashTag}</h2>

+<h3 id="polymer_41">Possible flash of unstyled content <a href="#polymer_41">#41</a></h3>

<p>Custom element found in document body without an "unresolved" attribute on it or

one of its parents. This means your app probably has a flash of unstyled content

before it finishes loading. See <a href="http://goo.gl/iN03Pj">http://goo.gl/iN03Pj</a> for more info.</p>

« no previous file with comments | « pkg/polymer/lib/src/build/build_filter.dart ('k') | pkg/polymer/lib/src/build/import_inliner.dart » ('j') | no next file with comments »