Bug 52711 – Performance issue while inserting CSS

• Status: RESOLVED
• Resolution: INVALID
• Component: CSS

[Aymeric Vitte]

This might be linked to bug 52561, while testing the workaround we posted for this bug, we discovered that CSS insertion is really slower with webkit compared to other browsers (FF for example)

This can be seen on http://www.extractwidget.com/mindex2test2.php (enter "parquet castorama" then OK), for each gadget the code before the alert is :

var d0=(new Date).getTime();

for (var i=0;i<currentCSS.length;i++) // currentCSS= array of CSS objects (LINK, STYLE)
{
zhead.$a(currentCSS[i]); //append CSS object to the head
};

alert((new Date).getTime()-d0);

As we can see the returned time for webkit based browsers is much higher than the one returned by FF for example.

On mobile devices, the returned time is in average 3 to 4 seconds per gadget on the iPhone 3G (!!!), 1s on android

[Alexey Proskuryakov]

*** Bug 52561 has been marked as a duplicate of this bug. ***

[Aymeric Vitte]

Bis from bug 52561 which is not resolved from our standpoint :

Try this please : http://www.extractwidget.com/mindex3.php

Then enter in the input "lit enfant 3suisses", then "OK", then pass the mouse over the search results, you will see appearing an iframe for each result with gadgets inside being loaded.

You will notice that quickly the browser seems to be blocked, scrolling on the iframes is not working well and while moving the mouse on the links the iframe does not change.

With webkit on a normal PC with ADSL it takes 3mn and 20 s with this test for the browser to recover and finish the job.

With FF it takes 1mn and 20 s and during that time you can use the scrolling and move from an iframe to another without the browser looking to be blocked.

Sorry to insist, there is really a performance problem somewhere, we have optimized everything on our side, we are not talking now about seconds on mobile devices against ms on a PC but about minutes on a PC connected to internet via adsl

[Brent Fulgham]

The test page no longer exists. We can't take action on this bug.