consider making properties that cannot be set synchronously read-only

RESOLVED FIXED

Status

Add-on SDK
General
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: myk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
I grow increasingly concerned about the ramifications of cross-process asynchronicity wrt. property setters, especially given recent conversation in bug 582808.

I am starting to think we should make a variety of properties that are currently read/write into read-only properties, at least until we figure out whether we can make them synchronously writable or must implement asynchronous methods for setting them.

I'm thinking particularly of the properties of Tab objects, but Widget and Panel also have some problematic properties.  Other interfaces may as well.

Marking this blocking, as we need to at least make a decision about it, whether or not we end up deciding to make these properties read-only.
(Reporter)

Comment 1

7 years ago
Issue considered, and I think we're actually ok.  More details are in the discussion group <http://groups.google.com/group/mozilla-labs-jetpack/browse_thread/thread/8b6fc54623ef1529>.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.