On Thu, 12 Aug 2010 14:24:10 +0200, Mike Wilcox
wrote:
I'm perplexed at the resistance. We've tried telling our clients not to
use IE6, "IE8 is much faster". But inevitably, we have to make it work.
This is not nytimes.com. There's http://whatwg.org/html and
http://whatwg.org/C available f
I'm perplexed at the resistance. We've tried telling our clients not to use
IE6, "IE8 is much faster". But inevitably, we have to make it work.
Mike Wilcox
http://clubajax.org
m...@mikewilcox.net
On Aug 11, 2010, at 8:29 PM, Boris Zbarsky wrote:
> On 8/11/10 9:17 PM, Garrett Smith wrote:
>> O
On 8/11/10 9:17 PM, Garrett Smith wrote:
On 8/11/10, Boris Zbarsky wrote:
On 8/11/10 11:48 AM, Boris Zbarsky wrote:
javascript:var start = new Date(); function f(n) { for (var k =
n.firstChild; k; k = n.nextSibling) f(k); } f(document); alert(new
Date() - start)
Er, that had a typo. The cor
On 8/11/10, Boris Zbarsky wrote:
> On 8/11/10 11:48 AM, Boris Zbarsky wrote:
>> javascript:var start = new Date(); function f(n) { for (var k =
>> n.firstChild; k; k = n.nextSibling) f(k); } f(document); alert(new
>> Date() - start)
>
> Er, that had a typo. The correct script is:
>
> javascript:v
On 8/11/10 11:48 AM, Boris Zbarsky wrote:
javascript:var start = new Date(); function f(n) { for (var k =
n.firstChild; k; k = n.nextSibling) f(k); } f(document); alert(new
Date() - start)
Er, that had a typo. The correct script is:
javascript:var start = new Date(); function f(n) { for (var
On 8/11/10 10:31 AM, Garrett Smith wrote:
It would have been more helpful to explain, if you can, the cause of
the slowness in Firefox..
Sure thing. https://bugzilla.mozilla.org/show_bug.cgi?id=481131#c12
(the paragraph starting "The time") and
https://bugzilla.mozilla.org/show_bug.cgi?id=48
On 8/11/10, Boris Zbarsky wrote:
> On 8/11/10 3:49 AM, Garrett Smith wrote:
>> I'm running Firefox 3.6.4 on windows 7
>
> Which has a known performance bug with a particular reasonably rare
> class of DOM mutations. The only way for the spec to avoid performing
> such mutations is to not add the
On 8/11/10 3:49 AM, Garrett Smith wrote:
I'm running Firefox 3.6.4 on windows 7
Which has a known performance bug with a particular reasonably rare
class of DOM mutations. The only way for the spec to avoid performing
such mutations is to not add the annotation boxes (which is what it will
On 8/10/10, Ian Hickson wrote:
> On Wed, 7 Jul 2010, Garrett Smith wrote:
>>
>> This is about the fourth time I've said it here. Can the person in
>> charge of writing the slow and buggy ajvascript on the HTML 5 spec
>> please remove that?
>>
>> The problem is that that whatwg page causes freezes
On Wed, 7 Jul 2010, Garrett Smith wrote:
>
> This is about the fourth time I've said it here. Can the person in
> charge of writing the slow and buggy ajvascript on the HTML 5 spec
> please remove that?
>
> The problem is that that whatwg page causes freezes and crashes [...]
That sounds like a
On 2010-07-08 19:18, Diego Perini wrote:
On Thu, Jul 8, 2010 at 4:03 PM, Lachlan Huntwrote:
As a workaround, you can use AdBlock in Firefox to block the offending
script. Just manually add this URL to your block list.
http://www.whatwg.org/specs/web-apps/current-work/status.js
The problem is
On 7/8/10, Lachlan Hunt wrote:
> On 2010-07-08 02:28, Garrett Smith wrote:
>> This is about the fourth time I've said it here. Can the person in
>> charge of writing the slow and buggy ajvascript on the HTML 5 spec
>> please remove that?
>>
>>
>> The problem is that that whatwg page causes freeze
On Thu, 2010-07-08 at 19:18 +0200, Diego Perini wrote:
>
>
>
> On Thu, Jul 8, 2010 at 4:03 PM, Lachlan Hunt
> wrote:
>
> On 2010-07-08 02:28, Garrett Smith wrote:
>
> This is about the fourth time I've said it here. Can
> the person in
>
On Thu, Jul 8, 2010 at 4:03 PM, Lachlan Hunt wrote:
> On 2010-07-08 02:28, Garrett Smith wrote:
>
>> This is about the fourth time I've said it here. Can the person in
>> charge of writing the slow and buggy ajvascript on the HTML 5 spec
>> please remove that?
>>
>>
>> The problem is that that wh
On Thu, Jul 8, 2010 at 5:35 PM, Henri Sivonen wrote:
> On Jul 8, 2010, at 00:45, Diego Perini wrote:
>
> > I do not see the reason of having a specification lecture also be a
> stress-test.
> >
> > As Aaron already said I just want to be able to read the specs.
> >
> > A button at the top maybe t
On Jul 8, 2010, at 00:45, Diego Perini wrote:
> I do not see the reason of having a specification lecture also be a
> stress-test.
>
> As Aaron already said I just want to be able to read the specs.
>
> A button at the top maybe to switch to the stress-test ?
It's not primarily a stress test.
On 2010-07-08 02:28, Garrett Smith wrote:
This is about the fourth time I've said it here. Can the person in
charge of writing the slow and buggy ajvascript on the HTML 5 spec
please remove that?
The problem is that that whatwg page causes freezes and crashes in Firefox. i
As a workaround, y
I do not see the reason of having a specification lecture also be a
stress-test.
As Aaron already said I just want to be able to read the specs.
A button at the top maybe to switch to the stress-test ?
Diego
On Thu, Jul 8, 2010 at 3:43 AM, Boris Zbarsky wrote:
> On 7/7/10 5:43 PM, Aaron Bood
On 7/7/10 5:43 PM, Aaron Boodman wrote:
I hear this every so often. Do we really need the spec to double as a
browser stress test? I mean, there are actual test suites nowadays. I
just want to read the spec.
I'll just note that part of the reason it's a "stress test", apart from
the old Firefo
On 7/7/10 5:28 PM, Garrett Smith wrote:
The problem is that that whatwg page causes freezes and crashes in Firefox.
May I recommend trying out Firefox 4 beta 1? ;)
-Boris
On Wed, Jul 7, 2010 at 5:43 PM, Aaron Boodman wrote:
> On Wed, Jul 7, 2010 at 5:41 PM, Tab Atkins Jr. wrote:
>> On Wed, Jul 7, 2010 at 5:28 PM, Garrett Smith wrote:
>>> This is about the fourth time I've said it here. Can the person in
>>> charge of writing the slow and buggy ajvascript on the
On 7/7/10, Tab Atkins Jr. wrote:
> On Wed, Jul 7, 2010 at 5:28 PM, Garrett Smith
> wrote:
>> This is about the fourth time I've said it here. Can the person in
>> charge of writing the slow and buggy ajvascript on the HTML 5 spec
>> please remove that?
>>
>>
>> The problem is that that whatwg pa
On Wed, Jul 7, 2010 at 5:41 PM, Tab Atkins Jr. wrote:
> On Wed, Jul 7, 2010 at 5:28 PM, Garrett Smith wrote:
>> This is about the fourth time I've said it here. Can the person in
>> charge of writing the slow and buggy ajvascript on the HTML 5 spec
>> please remove that?
>>
>>
>> The problem is
On Wed, Jul 7, 2010 at 5:28 PM, Garrett Smith wrote:
> This is about the fourth time I've said it here. Can the person in
> charge of writing the slow and buggy ajvascript on the HTML 5 spec
> please remove that?
>
>
> The problem is that that whatwg page causes freezes and crashes in Firefox. i
This is about the fourth time I've said it here. Can the person in
charge of writing the slow and buggy ajvascript on the HTML 5 spec
please remove that?
The problem is that that whatwg page causes freezes and crashes in Firefox. i
When it doesn't throw errors, it freezes Firefox.
This is is u
25 matches
Mail list logo
