On Sat, Jun 11, 2011 at 1:14 AM, Mateusz Harasymczuk
wrote:
> If someone moved out of the IE 6, then he/she move out of the IE 7, too.
while i agree, i found microsoft's tortuous path to standards full of
dark corners.
case in point: some time ago, i was using some simple pages.
of course, to g
Totally agree,
If someone moved out of the IE 6, then he/she move out of the IE 7, too.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/fAHtqn9esi
IE 7 should be probably dropped with IE6, I can't see point in keeping
it
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
On Fri, Jun 10, 2011 at 12:01 AM, Florian Apolloner
wrote:
> Hi,
>
> On Jun 9, 1:11 pm, Gert Van Gool wrote:
>> I remember from the HTML5 doctype that some people (with app in enterprises)
>> need the support
>
> Right, but even Google is dropping support for IE < 8 [1]! And if
> Google is trying
Hi,
On Jun 9, 1:11 pm, Gert Van Gool wrote:
> I remember from the HTML5 doctype that some people (with app in enterprises)
> need the support
Right, but even Google is dropping support for IE < 8 [1]! And if
Google is trying to get companies to use newer browsers we should
support that too ;)
C
;Carl Meyer"
>>to: django-developers@googlegroups.com
>>subject: [] Re: Deprecation policy for IE6
>>
>>On 06/09/2011 05:32 AM, Idan Gazit wrote:
>>> I'm looking at admin tickets, and I realize that some defined policy
>>> for when we can safely
On Thu, Jun 9, 2011 at 9:44 AM, Aymeric Augustin
wrote:
> c) need to access a Django application — let alone a Django >= 1.4 app.
even less likely: a Django application's admin page
--
Javier
--
You received this message because you are subscribed to the Google Groups
"Django developers" gro
2011/6/9 Idan Gazit
> I'm looking at admin tickets, and I realize that some defined policy for
> when we can safely start to break IE6 would be very helpful.
>
My vote is: "last year". Even Microsoft begs people to move away from IE6.
I can't think of a context where people:
a) can't upgrade
IE7 is almost just IE6 with tabs. In my opinion, going forward, IE
support should be IE8+.
Like said earlier, if someone really need support for IE7 and lower,
they can still use Django 1.3.
On Jun 9, 3:27 pm, Xavier Ordoquy wrote:
> Le 9 juin 2011 à 15:06, Henrik Genssen a écrit :
>
> > the q
Le 9 juin 2011 à 15:06, Henrik Genssen a écrit :
> the question is not - how old a browser is, but how many user it (still) has
> in germany there are still 4% using IE6 - thats
> half the user of Google's Chrome with 8%.
>
>
> Henrik
It looks like fewer german users are still running ie6.
htt
s@googlegroups.com
>subject: [] Re: Deprecation policy for IE6
>
>On 06/09/2011 05:32 AM, Idan Gazit wrote:
>> I'm looking at admin tickets, and I realize that some defined policy
>> for when we can safely start to break IE6 would be very helpful.
>>
>> I'd
OK, by the power vested in me, I declare the admin unshackled from the need to
support IE6.
Reception and dancing shall follow.
On Thursday, June 9, 2011 at 2:22 PM, Carl Meyer wrote:
> On 06/09/2011 05:32 AM, Idan Gazit wrote:
> > I'm looking at admin tickets, and I realize that some defined p
I've seen a few admin themes in the wild. Would it be fair to say that after
a certain (very near) date, if you need EOL browser support, it will have to
be provided by a 3rd party theme?
On Jun 9, 2011 7:11 AM, "Gert Van Gool" wrote:
> On Thu, Jun 9, 2011 at 12:32, Idan Gazit wrote:
>
>> I'm loo
On 06/09/2011 05:32 AM, Idan Gazit wrote:
> I'm looking at admin tickets, and I realize that some defined policy
> for when we can safely start to break IE6 would be very helpful.
>
> I'd like to simply declare that going forward, the admin need not
> work perfectly in IE6. That leaves our support
On Thu, Jun 9, 2011 at 12:32, Idan Gazit wrote:
> I'm looking at admin tickets, and I realize that some defined policy for
> when we can safely start to break IE6 would be very helpful.
>
> I'd like to simply declare that going forward, the admin need not work
> perfectly in IE6. That leaves our
I'm looking at admin tickets, and I realize that some defined policy for when
we can safely start to break IE6 would be very helpful.
I'd like to simply declare that going forward, the admin need not work
perfectly in IE6. That leaves our support footprint for the Admin at "modern
browsers" +
16 matches
Mail list logo
