Make WordPress Core

Opened 7 years ago

Closed 6 years ago

#9889 closed defect (bug) (invalid)

several scripts are very slow in Camino (and possibly FF)

Reported by: Denis-de-Bernardy Owned by: azaozz
Milestone: Priority: normal
Severity: minor Version: 2.8
Component: JavaScript Keywords:
Focuses: Cc:

Description (last modified by Denis-de-Bernardy)

Just realized this upon comparing it with Safari while investigating a css bug.

In Safari it's nice and snappy. In Camino (and possibly FF), there is 1s or more of lag when:

  • TinyMCE is loading in the editor
  • The widgets screen is loading

It seems related to performance differences between the jQuery selectors (dunno about the TinyMCE equivalent) in script engines.

Change History (8)

#1 @Denis-de-Bernardy
7 years ago

  • Description modified (diff)

the one for the admin menu only happens on the widgets script.

#2 @demetris
7 years ago

What version of Safari?

Safari 3.2 is faster than Fx 3.0. Safari 4 is *very* fast. Fx 3.1/3.5 is about as fast as Safari 4, but Fx 3.0 is much slower. I suppose the current stable version of Camino uses the same engines as Fx 3.0.

Was this comment helpful? [YES] [NO]

#3 @Denis-de-Bernardy
7 years ago

Camino 1.6.7.

Safari (3.2.3) is fine.

#4 @demetris
7 years ago


Camino 1.6.7 runs on Gecko 1.8.1, the same engine Fx 2 used. That’s very slow compared to the speed of engines in stable and beta browsers today (and even more slow considering the increasing amount of JS used in pages).

So, this slowness is to be expected.

See this table here for reference:


#5 @Denis-de-Bernardy
7 years ago

  • Milestone 2.8 deleted
  • Resolution set to invalid
  • Status changed from new to closed

that explains a lot, yes.

#6 @ryan
7 years ago

Just FYI, TinyMCE uses Sizzle, just like jQuery.

#7 @Denis-de-Bernardy
6 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#8 @Denis-de-Bernardy
6 years ago

  • Resolution set to invalid
  • Status changed from reopened to closed

sorry, wrong ticket

Note: See TracTickets for help on using tickets.