Fabian Guisset wrote: > dwx wrote: > >> cookperm.txt >> > > [cookperm.txt doc here] > > dwx: great work! that's what I call initiative :-) > > If you don't mind, I already uploaded it temporarily as html at > http://moz.zope.org/Members/fabian/drafts/cookperm.txt > until I can figure out the right URI (again, if you agree to put it on > moz.zope.org. I can't help you put it up on mozilla.org right now): > /dev/cookies/cookperm.txt or /dev/profile/cookperm.txt or somewhere else? > > -Fabian. >
Is there a similiar mechanism for other parts of the browser? I.e. what I'm thinking about is, a mechanism of linking from a wep page to such or a similiar perission file, which defines, which javascript elements generated from which documents (identified by their source URI) may access which Javascript and DOM objects to read or modify them to controll security in detail. I don't like the ancient domain binding of security, because this is too raw and domain names do not match authors. Multipl domaons may belong to the same autor and one singel domain may host stuff from many authors. So domain naims are no aspect for security rights management. Also allowing or denying acces to the whole document is not allways desired. So I would like to controll this in detail for each document and document individual. Is there something like the cookperm.txt to control such other stuff? Where can I find info about such amechanism? -- Georg Maa� - bioshop.de D-84082 Laberweinting, Hofkirchen 96 JavaScript, C++ Engineering - The ultimative DHTML engine: http://gml-modul.sourceforge.net - http://sourceforge.net/projects/gml-modul
