I think I noticed this. I think the "kill javascript on any javascript runtime" code from ebjs is triggered prior to the seg fault. But it's tricky to grasp what happened, because of what we've been saying in the recent messages about this ebjs code: it gets buried by the rest of the db5 output. But I think Karl just went ahead with changing this to quit eb immediately. Now, I think if you go through these motions (javascript disabled but no seg fault) you actually can indeed read Raw Story articles. So it is sort of like the right thing happening for the wrong reasons. It still could be seen as a good thing but it is capricious, because Raw Story did not happen to hold their plain text hostage to successful JS completion, but unfortunately a lot of other sites do.
Kevin _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
