Derrell Lipman

In fact, this code that you presented above is implemented almost exactly like that, in `setXxxAsync()`. You just need to use `setXxxAsync()` and not `setXxx()` to get the desired behavior.

I'd like @oetiker's comments too. I already agreed, somewhat reluctantly, to have the sync setter change the stored value of the property once the promise which was set in that...

A sync setter's apply is expected to be synchronous, traditionally. I may be able, however, for synchronous `setXxx()` calls, to obtain the return value of the `apply` method, and if...

And what happens if `apply` returns a promise (recall that `setXxx()` returns before it resolves), and `setXxx()` is called again? This begins to incur the same chaining requirement as `setXxxAsync`,...

I am trying to retrofit promise support into the sync setter. This method no longer works propertly for normal (non-property) set, now that I've mucked with it. I don't understand...

Thanks. I believe the referenced code in that snippet doesn't do anything because the return value of `.then` is ignored... but there's nothing to do with it, because `__applyAndFireEvent` method...

Let me attempt to absorb this. Yes, `this` should have been `proxy` (copy/paste and lack of understanding causing that error). For `setXxxAsync`, the implementation uses `await` and (I think) works...

`getPropertySetCompletePromise` is never called. When is it supposed to be used?

`__applyAndFireEvent` does not return a value since it is used only for the synchronous setter. Therefore the lines at the end don't serve any purpose in this implementation, I think:...

Interestingly, the indigo theme is missing an entry for "table-editor-textfield"