[theme-reviewers] Possible additions to Theme Unit Test data

[Chip Bennett]

Into your test site: yes. But the Theme Unit Data are hosted on wpcom.

The last time I tried to add form fields, it just wouldn't work. Maybe
something's changed now. Send me some test data (off-list), and I'll try to
add them to the TUT data.

Chip

On Mon, Apr 30, 2012 at 10:02 PM, Amy Hendrix <sabreuse at gmail.com> wrote:

> Confirming Emil's impression - I just C/P'ed George's sample into my
> test site, and the HTML comes through fine. I suspect things would get
> stripped if it were a form trying to send anywhere.
>
> On Mon, Apr 30, 2012 at 10:56 PM, Emil Uzelac <emil at themeid.com> wrote:
> > I was under the impression that this was CSS related! Am I missing
> > something?
> >
> > e.g. input[type='button'], input[type='submit'], input[type='reset']
> >
> > Emil
> >
> > On Mon, Apr 30, 2012 at 9:49 PM, Chip Bennett <chip at chipbennett.net>
> wrote:
> >>
> >> Form fields can't go in Post Content. They just simply won't save or
> >> import. They get filtered by post_kses (I think).
> >> The best we can do, I think, is the comment form fields.
> >>
> >> As for the language support: how feasible/reasonable would that be for
> the
> >> testers to test?
> >>
> >> Chip
> >>
> >> On Mon, Apr 30, 2012 at 9:01 PM, Amy Hendrix <sabreuse at gmail.com>
> wrote:
> >>>
> >>> Hey all,
> >>>
> >>> I just had a conversation in IRC with George Stephanis from the core
> >>> UI crew. They're planning to add styling for several of the HTML5
> >>> input types (input type="date", type="url", and so on) to Twenty Ten
> >>> and Twenty Eleven, and he asked if we could add a set of form fields
> >>> to the Theme Unit Test data.
> >>>
> >>> The proposed theme changes are here:
> >>> http://core.trac.wordpress.org/ticket/20579
> >>> And HTML for the unit test is here: http://cl.ly/2E3M103q1V2s3k1Z0X1w
> >>>
> >>> We don't require HTML5, at least not yet, so it would clearly be out
> >>> of our scope to require the new input types, but I *do* think it would
> >>> be worth adding a page to the Layout Test for form elements even
> >>> without making it a review requirement: ugly (or inconsistent) default
> >>> form elements are UGLY, and the Theme Unit Test is useful as an
> >>> education and testing tool as much as a part of the review.
> >>>
> >>>
> >>> As a separate request, I'd also like to see us add a multilingual
> >>> content test: even though we default to English for the main theme
> >>> language, themes should still be able to handle non-English *content*
> >>> whether it's extended-Latin, Cyrillic, RTL, Asian, etc. Even with the
> >>> correct database encoding, designs can get pretty ugly with the wrong
> >>> meta charset or even bad font choices. I'd love to see a Layout Test
> >>> section with quotes in a few of the more common character sets; I
> >>> suspect there are people on this list who can come up with a far
> >>> better variety of both languages and quotes than I can ;)
> >>>
> >>> What say we?
> >>>
> >>> A.
> >>> _______________________________________________
> >>> theme-reviewers mailing list
> >>> theme-reviewers at lists.wordpress.org
> >>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>
> >>
> >>
> >> _______________________________________________
> >> theme-reviewers mailing list
> >> theme-reviewers at lists.wordpress.org
> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>
> >
> >
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120430/a83ee2ac/attachment.htm>