On Dec 1, 2009, at 2:01 PM, Ryan Grimm wrote:
Hi Geoff,
So I take it that I'm understanding the API correctly? I'm
currently using the WebKit framework bundled with the latest version
of Safari. Should I go ahead and file a bug report?
Please do. Your understanding is correct, what you wrote should create
a read-only property. You may also want to check if it happens if you
link against the latest WebKit nightly, to verify the bug is still
present.
- Maciej
--Ryan
On Dec 1, 2009, at 12:28 PM, Geoffrey Garen wrote:
Sounds like a bug.
Geoff
On Dec 1, 2009, at 11:10 AM, Ryan Grimm wrote:
Hi,
I'm using the JavaScriptCore (Mac) API to add some properties into
the javascript environment and would like to make sure that these
properties are read only from the javascript side. From the looks
of the API, I thought adding the properties with calls like this
would do the trick:
JSObjectSetProperty(ctx, globalObject, propertyName,
propertyValue, kJSPropertyAttributeDontDelete |
kJSPropertyAttributeReadOnly, NULL);
The property gets added without any troubles but in javascript
(and the Web Inspector) I can modify and delete the properties
that I've added. Am I I missing something or just reading the
docs wrong?
Thanks.
--Ryan
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
