Hi all,
With no objections that weren't addressed, I've committed this change now.
Just to re-iterate - we've switch the admin and other templates to an
HTML5 doctype, but that doesn't mean we are dropping support for older
browsers. We will continue to be selective and conservative in the use
of
FYI, I've just stumbled on ticket #7452 and this thread:
http://groups.google.com/group/django-developers/browse_thread/thread/f346813ab89d4155/
One interesting idea that was suggested is to introduce a setting for
controlling the type of HTML.
--
You received this message because you are subscr
2011/3/30 Łukasz Rekucki
> On 30 March 2011 06:55, Matt Harasymczuk wrote:
> >
> > Most of users has JS enabled browsers, if so, modernizr works.
> > Otherwise jQuery will not work either.
>
> Most is not all. Even now the admin will work without jQuery, but it
> won't work without modernizr if
On 30 March 2011 06:55, Matt Harasymczuk wrote:
>
> Most of users has JS enabled browsers, if so, modernizr works.
> Otherwise jQuery will not work either.
Most is not all. Even now the admin will work without jQuery, but it
won't work without modernizr if you put HTML5 tags in it.
>
> I can't r
Maybe start thinking in other way.
Most of users has JS enabled browsers, if so, modernizr works.
Otherwise jQuery will not work either.
I can't remember when someone who has IE6 hit one of my django based
sites.
Maybe convert django to html5, and those who has to care about ie6
support should o
I think it would be helpful here to clearly distinguish three distinct
varieties of "using HTML5," two of which are clear wins and one which I
don't see any reason to do:
1. Switching to the HTML5 doctype in those few places where Django
actually renders a full page with doctype (the admin, databr
On 29/03/11 04:29, Julien Phalip wrote:
> Since the patch is small, then it would be very quick to test it in
> all browsers right away, no? :-)
I've spent 20 minutes testing out the admin with this patch and IE6, and
haven't found any issues (at least, none that aren't already present
without th
On 29/03/11 05:52, Gabriel Hurley wrote:
> Switching to the HTML5 doctype won't hurt IE6 rendering (having dealt
> with this myself several times). To the best of my knowledge--from my
> own tests and third-party sources--using the new input attributes also
> doesn't hurt IE6. However, if we start
Using HTML5 tags in IE _will_ break it at some point. There is ofcourse the
work around with "document.createElement('article')" etc used by modernizr
But:
1. This will not work for IEs' that have JS disabled
2. Will break if you insert HTML5 tags by javascript into the "innerHTML"
attribute of
How about delivering http://www.modernizr.com/ library.
In my case it solves all problems with non existing tags (nav,
section, header, article, footer) in such browsers as IE.
We ship jQuery with admin, why not use modernizr to support legacy
browsers.
I am positive, about input types fallback t
On Mar 29, 4:01 pm, Stephen Burrows
wrote:
> 3. There is a simple workaround going back to ie6 for handling the css
> problems related to unrecognized tags. [3]
...snip...
> [3]http://diveintohtml5.org/semantics.html#unknown-elements
The workaround works if javascript is enabled. So we can't co
Anyone interested in reading about html5 can find a lot of great
information at http://diveintohtml5.org/.
Some of the highlights:
1. a change to the doctype of the admin from http://www.w3.org/TR/xhtml1/DTD/xhtml1-
strict.dtd"> to should still keep ie6 in Almost
Standards Mode [1]
2. Browsers
Switching to the HTML5 doctype won't hurt IE6 rendering (having dealt with
this myself several times). To the best of my knowledge--from my own tests
and third-party sources--using the new input attributes also doesn't hurt
IE6. However, if we start delving deeper into HTML5 and using the new HT
On Mar 29, 2:29 pm, Julien Phalip wrote:
> On Mar 29, 1:26 pm, Luke Plant wrote:
>
> > The further enhancements I'm thinking of are things like an EmailInput
> > widget (which I'd suggest was the default widget for EmailField, but
> > could be just available in django/forms/widgets.py). This widg
On Mar 29, 1:26 pm, Luke Plant wrote:
> The further enhancements I'm thinking of are things like an EmailInput
> widget (which I'd suggest was the default widget for EmailField, but
> could be just available in django/forms/widgets.py). This widget would
> output . AFAIK, this is fully backwards
On Tue, Mar 29, 2011 at 10:26 AM, Luke Plant wrote:
> On 29/03/11 03:10, Russell Keith-Magee wrote:
>> Of course, this depends a great deal on the details of exactly what is
>> to be done, and where. Luke's proposal says we should "use HTML5
>> features at least as an option in places like the adm
On 29/03/11 03:10, Russell Keith-Magee wrote:
> Of course, this depends a great deal on the details of exactly what is
> to be done, and where. Luke's proposal says we should "use HTML5
> features at least as an option in places like the admin", but the
> provided patch is a unilateral switch to HT
On Tue, Mar 29, 2011 at 6:08 AM, Wim Feijen wrote:
> +1. All major browsers now support html5 and by the time django 1.4
> will be released we will be right on time though a bit late.
Statements like "All modern browsers support it" misses the point. It
isn't the *modern* browsers that are the is
+1
No harm, as it breaks nothing currently using the templates.
Sets a great message that Django moves forward. I like it.
On Mon, Mar 28, 2011 at 12:38 PM, Luke Plant wrote:
> Hi all,
>
> I'd like to put forward the proposal that we switch to HTML5 for all
> Django supplied templates in Django
+1. All major browsers now support html5 and by the time django 1.4
will be released we will be right on time though a bit late.
In response to Gabriel, in my opinion, legacy problems should not be
addressed by not moving forward, but they can be resolved by either 1.
updating or 2. staying on a l
While on a personal level I agree wholeheartedly about moving to HTML5, I do
have reservations about it from the perspective of Django's "enterprise"
customers (AKA the ones with legacy and bureaucratic issues).
Thankfully we don't have major backwards-compatibility issues to deal with
from a f
As with the others, I'll chime in to support this idea. It will really
help move Django in the direction that the web is going, without
seriously breaking existing code (aside from the people who are really
using the XHTML features, and those people can almost certainly figure
out how to change bac
I agree completely that we should move to HTML5. It seems like it will be
even more important as more and more people use Smart Phones or Pads for
surfing the net, and I believe all of these are supporting HTML5. I've
started attending some HTML5 user group meetings, and I'm quite impressed
with t
Hi Luke,
On 03/28/2011 12:38 PM, Luke Plant wrote:
> Overall, I think the advantages outweigh the disadvantages, that we have
> to make the move sometime, and now is about the right time, or perhaps
> slightly late.
100% agreed, for all the reasons you outlined. We've been using the
HTML5 doctype
24 matches
Mail list logo
