So how about rebuild the gjs package against seamonkey 2.7? Some attempt to rebuild gjs package to use seamonkey 2.7 were not success at all. The js API that being used within gjs were not compatible with seamonkey 2.7. So it will make the compilation failed. There are still no patches or fix from gjs developer (GNOME developer) about this API changes. So it must be another way to make gnome-shell works again.
Several days ago, I accidentally take a look the configure script of gjs and just found out that gjs could be compiled against mozjs185. Mozjs185 itself is a pkg-config name for SpiderMonkey. Some words about SpiderMonkey from Wikipedia:
So without anymore doubt, I am finally rebuild my gjs package against mozjs185 which I have already use for the 0ad game package. At first built, I have derived the opensuse mozjs185.spec configuration. And later on, I got an email reply from Robby Workman about his works on mozjs185 (Robby uses a name of js185) and I rebuilding my mozjs185 package using his slackbuild configuration with some modification. Robby's SlackBuild is using additional nspr library which is built and installed before building mozjs185. So Robby's js185.SlackBuild is using --with-system-nspr option. I prefer to preserving the compatibility with slackware by using seamonkey nspr library. So I am using these options to build the mozjs185:
--enable-threadsafe \ --with-nspr-cflags="`pkg-config --cflags nspr`" \ --with-nspr-libs="`pkg-config --libs nspr`"
So that's my solution for the gnome-shell versus seamonkey troubles. How about you?