Until this is fixed, I just wanted to document a workaround for UTF-8 
problems: add an appropriate meta tag to the top of the imported file 
(e.g., imported Polymer element definition):

<meta charset="utf-8">

This works in both Canary and polyfilled browsers. It's unfortunate to have 
to include this in every file that contains UTF-8 (I often use Unicode 
characters as icon glyphs, for example), but at least it's easy enough to 
do. Once the question of how HTML Imports should assume UTF-8 is resolved, 
the meta tag can be removed.

On Tuesday, April 8, 2014 4:54:19 PM UTC-7, John Messerly wrote:
>
> On Tue, Apr 8, 2014 at 4:05 PM, Hajime Morrita 
> <[email protected]<javascript:>
> > wrote:
>
>> Jan:
>> Well, this is something we have to decide how it should work. There are 
>> some discussion on spec side but I agree that it's time to roll it up.
>>
>> John:
>> Quirks thing is tricky and Blink might need some polish there.
>> Even if there are quirks mode of imports, rendering is happening in the 
>> main ("master") document. It is not clear what quirks mode for imports 
>> means. My gut feeling is that it should follow the mode of the master 
>> document. 
>>
>
> makes sense :).
>
> I doubled check the HTML parsing spec (and html5lib implementation) and 
> there I only found one example of quirks affecting parsing:
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#parsing-main-inbody,
>  
> under `A start tag whose tag name is "table"`. But it's somewhat obscure, 
> and only prevents an open <p> from being closed by a <table>. So perhaps 
> not a big deal after all.
>
>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/62a05bb4-63fd-4c04-838e-33feb9cb8072%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to