Huh? Break existing extensions? We don't have any extensions that we don't control (IOW: we can fix all of them), so what's the point in keeping this "compatibility with nothing"?
-- Gustavo Sverzut Barbieri Intel Open source Technology Center From: [email protected] [mailto:[email protected]] On Behalf Of Huo, Halton Sent: Tuesday, September 17, 2013 12:38 AM To: Oliveira, Caio; Huang, Deqing Cc: [email protected] Subject: Re: [Crosswalk-dev] How to mark read-only for root of a extension > The way we are exposing things right now, Crosswalk creates the object. If > the behavior makes sense, we could simply change it to make that object > read-only after the JS API code ran. Do you want to mark root object read-only unconditionally? It can satisfy the Tizen Device API needs. But I'm not sure whether all Spec define read-only of root. Alternatively, extension framework could offer a new api bool read_only const { return read_only_; } By default, return true, so that it won't break the existing extensions. Thanks, Halton.
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
