GNOME Bugzilla – Bug 630539
xulrunner 1.9.3+ patches
Last modified: 2010-09-30 16:43:59 UTC
Basically straightforward stuff, though I didn't check for other string.replace uses.
Created attachment 171048 [details] [review] Support xulrunner 1.9.3+ Add small wrappers around JS_AddValueRoot. Add JS_BeginRequest in our custom code.
Created attachment 171049 [details] [review] telepathy: Use string.replace in a way compatible with newer Spidermonkey The semantics of the first argument changed from literal -> regexp if the 'g' option was specified. To remove ambiguity, stop using the spidermonkey extension and create a standard RegExp object.
Created attachment 171050 [details] [review] telepathy: Use string.replace in a way compatible with newer Spidermonkey Fix the other user I saw
Review of attachment 171050 [details] [review]: Good
Review of attachment 171048 [details] [review]: Looks good, a style comment about the configure.ac change ::: configure.ac @@ +117,3 @@ +if test "x$have_js_newglobalobject" = xtrue; then + AC_DEFINE(HAVE_JS_NEWGLOBALOBJECT, 1, + [Define if -lmozjs has NewGlobalObject]) Can't you just add JS_NewGlobalObject into the AC_CHECK_FUNCS where sn_startup_sequence_get_application_id is checked? (The comment above needs a littel adjustment if you do that)
*** Bug 624745 has been marked as a duplicate of this bug. ***
Attachment 171048 [details] pushed as 11db188 - Support xulrunner 1.9.3+ Attachment 171050 [details] pushed as e22fbda - telepathy: Use string.replace in a way compatible with newer Spidermonkey