On Aug 7, 2010, at 10:39 PM, Mitar wrote: > Hi! > > On Sun, Aug 8, 2010 at 6:10 AM, Noah Kantrowitz <[email protected]> wrote: >> Switching to HTML5 will require a lot more than simply changing the doctype. > > Hm. As far as I researched XHTML 1.0 Strict with HTML5 doctype is > valid HTML5. Changes are that HTML5 parsers parse more than XHTML and > how they are handling errors. And of course new tags. But producers > can still produce XHTML, only doctype should be changed so that > browsers know we are talking HTML5 and by using doctype we are still > X(HT)ML valid. > > And Genshi supports whichever tag you give, tag.video() and we are there. ;-) > > http://wiki.whatwg.org/wiki/HTML_vs._XHTML > >> Show that the tests all pass and there are no security issues due to >> differing serialization rules and you will find more support. > > But would you agree on including such changes if they are proven to > work? Do you agree on the approach? Configuration option, browser > dependent doctype? > > Oh, we do even not need HTML5 as it seems jQuery: > > $('input:file').attr('multiple','multiple'); > > does the trick to allow input file element to select multiple files. > Of course only Trac should now allow multiple files coming through a > form. And post-processing them.
My point is more that if you are looking for a promise that the feature will be accepted, there is none to be found. It would depend on a number of factors like how big a change it is and how disruptive to the rest of the code it would be. For example, would this break compatibility with existing plugins? Given that the only answers to most of these questions can come from looking at the finished code, your best bet is to start there. --Noah -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
