From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 5F48D79370 for ; Wed, 10 Jun 2015 22:20:56 -0700 (PDT) Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-04v.sys.comcast.net with comcast id etNA1q0012LrikM01tNAFa; Thu, 11 Jun 2015 05:22:10 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-12v.sys.comcast.net with comcast id etN91q00K5LMg2101tN91l; Thu, 11 Jun 2015 05:22:10 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.4.1+ Date: Thu, 11 Jun 2015 01:22:09 -0400 Message-ID: <20150511012209.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1434000130; bh=R6aalnqgX2ulXCWXjNsXn3oJb/VfcEqs5MKJElfJd10=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=pV93kXSgkYm+FNjJAmS3ubQBaQl/N/6nvDUSuoz+DLPpMYD1YYtRrx7yulUMNwXYo 5wSVcGOqlef/9OHpF+vbew4GvKa/uBZfeHrR0sEOX6IZ90YPUqridX5krNqMKzW1Y4 xNaqZlOrmNO/2bFfaO4kWsFrtnFiR5B4iCce5H+3bG0ZyFbcC3mct93/3L/bHA6aBV QxL6CHcDU/3u/W83+Ks/YOJT43GY6j15rA/WRokJ6QooSxOYmy6+W8L24bJK4K1LYc 33U52yaKCODo5Z0Em1qdi6kxmePqyf+qCXakRFnLti9Vf1AePfFTDhXeLwahTehJEg xuIt9KhZVTxDA== Subject: [Edbrowse-dev] js engine strings X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2015 05:20:56 -0000 I converted all the jseng-moz.cpp strings from c++ to c, using the usual string management routines. The only c++ constructs are those required by the mozilla api. It should be easy now to convert this to a c process, as in duktape. Along the way I found and fixed a bug related to document.cookie. This is a doorway to set and read cookies. document.cookie = "foo=1"; document.cookie = "bar=2"; alert(document.cookie); This should print foo=1; bar=2 but it only retained the last cookie, and would show bar=2 A lot of websites rely on cookies, and don't work right without them, and some of these sites use javascript to manage cookies, so it's important that we get this one right. As usual, the bug went unnoticed because it was not tested in jsrt. I added a test for this now. Karl Dahlke