- From: Scott Wilson <scott.bradley.wilson@gmail.com>
- Date: Wed, 16 Sep 2009 18:22:09 +0100
- To: public-webapps WG <public-webapps@w3.org>
- Message-Id: <BB4BAADE-005F-4750-A2C5-E6F9D23E2D1D@gmail.com>
Marcos suggested some possible solutions to the issue of implementing protected preferences in the storage area using a pure JavaScript solution, and I've implemented some changes to Apache Wookie (incubating) which I think moves us closer to conformance. I've tested this on Firefox 3.5b and Safari 4 and it works OK - we may have problems with IE, but haven't done the testing yet. However in principle we can state that the variety of syntax used to address preferences, and the requirement to throw NO_MODIFICATION_ALLOWED_ERR on attempting to set a protected key, can be supported in a JS solution. So this resolves the issue I raised, and I'm happy with section 5.1. === The actual code is (currently - we're still in the process of moving all code over to the Apache repository) here: http://tencompetence.cvs.sourceforge.net/viewvc/tencompetence/wp6/org.tencompetence.widgetservice/WebContent/shared/js/wookie-wrapper.js?view=markup For testing the API we created a widget that exercises various aspects of the spec; you can download it here if you like: http://tencompetence.cvs.sourceforge.net/viewvc/tencompetence/wp6/org.tencompetence.widgetservice/widgets/test.wgt === -S PS thanks, Marcos for helping with this one!
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Wednesday, 16 September 2009 17:22:48 UTC