<font color="#333333"><font><font face="arial,helvetica,sans-serif">I don't believe so, why would e.g. input[type='submit'] get filtered by post_kses or anything else, isn't this being applied from style.css?<br>
</font></font></font><br><div class="gmail_quote">On Mon, Apr 30, 2012 at 9:58 PM, Amy Hendrix <span dir="ltr"><<a href="mailto:sabreuse@gmail.com" target="_blank">sabreuse@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Mon, Apr 30, 2012 at 10:49 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
> Form fields can't go in Post Content. They just simply won't save or import.<br>
> They get filtered by post_kses (I think).<br>
> The best we can do, I think, is the comment form fields.<br>
<br>
</div>Well, shoot. Didn't even think of that.<br>
<div><br>
> As for the language support: how feasible/reasonable would that be for the<br>
> testers to test?<br>
<br>
</div>Shouldn't be a very big problem -- we don't need testers to be able to<br>
read everything, but it's generally pretty easy even for non-speakers<br>
to tell the difference between properly rendered characters and the<br>
squares/question marks/black diamonds you get with improper encoding<br>
or missing glyphs.<br>
<br>
Since we're starting from <a href="http://wp.com" target="_blank">wp.com</a> and 2011, I'm pretty confident that<br>
sample content can be copy/pasted into the unit test blog and exported<br>
with the export tool with no problem.<br>
<div><div><br>
> Chip<br>
><br>
> On Mon, Apr 30, 2012 at 9:01 PM, Amy Hendrix <<a href="mailto:sabreuse@gmail.com" target="_blank">sabreuse@gmail.com</a>> wrote:<br>
>><br>
>> Hey all,<br>
>><br>
>> I just had a conversation in IRC with George Stephanis from the core<br>
>> UI crew. They're planning to add styling for several of the HTML5<br>
>> input types (input type="date", type="url", and so on) to Twenty Ten<br>
>> and Twenty Eleven, and he asked if we could add a set of form fields<br>
>> to the Theme Unit Test data.<br>
>><br>
>> The proposed theme changes are here:<br>
>> <a href="http://core.trac.wordpress.org/ticket/20579" target="_blank">http://core.trac.wordpress.org/ticket/20579</a><br>
>> And HTML for the unit test is here: <a href="http://cl.ly/2E3M103q1V2s3k1Z0X1w" target="_blank">http://cl.ly/2E3M103q1V2s3k1Z0X1w</a><br>
>><br>
>> We don't require HTML5, at least not yet, so it would clearly be out<br>
>> of our scope to require the new input types, but I *do* think it would<br>
>> be worth adding a page to the Layout Test for form elements even<br>
>> without making it a review requirement: ugly (or inconsistent) default<br>
>> form elements are UGLY, and the Theme Unit Test is useful as an<br>
>> education and testing tool as much as a part of the review.<br>
>><br>
>><br>
>> As a separate request, I'd also like to see us add a multilingual<br>
>> content test: even though we default to English for the main theme<br>
>> language, themes should still be able to handle non-English *content*<br>
>> whether it's extended-Latin, Cyrillic, RTL, Asian, etc. Even with the<br>
>> correct database encoding, designs can get pretty ugly with the wrong<br>
>> meta charset or even bad font choices. I'd love to see a Layout Test<br>
>> section with quotes in a few of the more common character sets; I<br>
>> suspect there are people on this list who can come up with a far<br>
>> better variety of both languages and quotes than I can ;)<br>
>><br>
>> What say we?<br>
>><br>
>> A.<br>
>> _______________________________________________<br>
>> theme-reviewers mailing list<br>
>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
>> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br>