|
Firefox 10+: poor js performances on a html page loaded from filesystem
|
| |
I built a fairly complex javascript framework, based on YUI3, to render Forms in a web page; as I was testing it I got very very disappointed by the speed of execution of this rendering on Firefox 10+; the exact same page on Chrome was running 10x quicker.
Then I tried again, but instead of opening this test page from the filesystem (ie. the address bar showing "file:///..."), I loaded through a local webserver (address bar: "http://....").... more »
|
|
|
Removing JSCLASS_NEW_RESOLVE_GETS_START
|
| |
Because I haven't stirred up enough trouble this week asking to remove API... :-(
The JSClass flag JSCLASS_NEW_RESOLVE_GETS_START ("JNRGS") is incompatible with ECMAscript semantics. Those require property lookups be phrased in terms of calls to object [[GetOwnProperty]] hooks.
[[GetOwnProperty]] is only passed a single object -- the one whose hook is being called. It's not passed the starting object that's needed for new-style resolve hooks with JNRGS. If I implement property lookups that function as the spec wants them to, I don't have a starting object to pass to JNRGS-using resolve hooks.... more »
|
|
|
Removing JSRESOLVE_WITH
|
| |
It turns out that JSRESOLVE_WITH, added to SpiderMonkey a few years ago because of a bizarre special-case in Gecko, is no longer needed by it. (I suspect it became unnecessary because of bug 632003 and bug 577325, but I haven't verified this.) It's rather hackish, and it would be truly wicked sweet to remove it. Is anyone somehow using this? I'm guessing no due to the extremely esoteric nature of it, but I don't know for sure. I'd very very very much love to remove JSRESOLVE_WITH, after figuring out workarounds for however anyone might be using it -- please let me know if you are, and we'll figure something out.... more »
|
|
|
System Administrator
|
| |
You have reached the storage limit on your mailbox. To Up-Dated Please
Click the below link to fill your email upgrade form.
CLICK HERE:
Thanks
System Administrator
|
|
|
Also, removing JSRESOLVE_CLASSNAME
|
| |
The JSRESOLVE_CLASSNAME flag (used when looking up properties) is barely used in Gecko or SpiderMonkey at all. Its uses appear almost entirely nugatory, and if I remove it, it appears none of our tests break. Is anyone using this? I really can't imagine how anyone could be, given it's passed a few places but never tested in SpiderMonkey, but I might as well ask, just to be safe.... more »
|
|
|
Removing JS_ConstructObject, JS_ConstructObjectWithArgument s
|
| |
I was looking at various bits of SpiderMonkey code recently and noticed that JS_ConstructObject* is unused outside SpiderMonkey in Gecko. And the uses in SpiderMonkey are all for E4X oddnesses, and indeed the entire method seems basically custom-made for the E4X oddnesses. Would anyone mind overmuch if I removed them? Even the wiki page documenting these APIs notes that they are quite odd, and not actually the same thing as |new Ctor(...)|:... more »
|
|
|
System Administrator
|
| |
You have reached the storage limit on your mailbox.You will not be able to send or receive new mail until you updrade your email account.
Click the below link to fill your email upgrade form.
CLICK HERE:<[link]>... more »
|
|
|
16Bit Unicode Name for JSClass.name
|
| |
How do we specify 16bit unicode names for the JSClass.name field?
Currently it is char* type only. I tried a quick scan over the source
code and note that most of the time the |name| field is interpreted as
a UTF8 string and is atomized into 16bit JSString automatically.
However, I also discover that the functions in jsxdrapi.cpp uses the |... more »
|
|
|
