OLD | NEW |
1 <!doctype html> | 1 <!doctype html> |
2 <!-- | 2 <!-- |
3 This file is autogenerated with polymer/tool/create_message_details_page.dart | 3 This file is autogenerated with polymer/tool/create_message_details_page.dart |
4 --> | 4 --> |
5 <html> | 5 <html> |
6 <style> | 6 <style> |
7 @font-face { | 7 @font-face { |
8 font-family: 'Montserrat'; | 8 font-family: 'Montserrat'; |
9 font-style: normal; | 9 font-style: normal; |
10 font-weight: 400; | 10 font-weight: 400; |
(...skipping 622 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
633 | 633 |
634 <div id="web_components_4"><h3>Error while inlining an import <a href="#web_comp
onents_4">#4</a></h3> | 634 <div id="web_components_4"><h3>Error while inlining an import <a href="#web_comp
onents_4">#4</a></h3> |
635 <p>An error occurred while inlining an import in the web_components build. This
is | 635 <p>An error occurred while inlining an import in the web_components build. This
is |
636 often the result of a broken HTML import.</p> | 636 often the result of a broken HTML import.</p> |
637 <p>One possible cause is using an @HtmlImport containing a relative path from | 637 <p>One possible cause is using an @HtmlImport containing a relative path from |
638 within an inline script tag, see http://goo.gl/ZgrhaV. The workaround currently | 638 within an inline script tag, see http://goo.gl/ZgrhaV. The workaround currently |
639 is to use a <code>package:</code> url instead, move the code to a dart file, or
simply | 639 is to use a <code>package:</code> url instead, move the code to a dart file, or
simply |
640 adding a real html import (since you are already in an html file).</p> | 640 adding a real html import (since you are already in an html file).</p> |
641 </div><hr /></body> | 641 </div><hr /></body> |
642 </html> | 642 </html> |
OLD | NEW |