elementId issue binding to an immutable computed property

[alexdiliberto]

The following JSBin is on beta:

http://emberjs.jsbin.com/temiji/2/edit

I would expect something like this to work but the component's final id in the DOM is actually being injected into the as to toString'd version of the computed property.

id="[object Object]"

If I bind elementId directly to a "String" literal it will work.

[alexdiliberto]

Also for more context, This issue occurs in v1.10 as well.

I updated the example to be v1.9.1 compatible...then it will simply ignore my CP and use the auto-generated id

http://emberjs.jsbin.com/puraqu/1/edit

[rwjblue]

Seems like this may be a duplicate of #10607 (which should have been fixed by #10613). Can you confirm/deny?

[alexdiliberto]

I don't think that one fixes this. I also tested this on beta/canary (first JSBin)

@rwjblue Some weird behavior also when I explicitly pass in the id vs set the elementId on the component http://emberjs.jsbin.com/temiji/5/edit?html,js,output

Really what I'm trying to achieve is an ID set using a CP though

[rwjblue]

I'm not seeing where this was ever supported (I could be wrong). We assume that calling this.elementId will return a plain string in many many places.

I believe that this isn't a bug/regression, but simply something that we do not support. I'd be in favor of documenting that explicitly in the API docs (around here).

The following JSBin shows a way to get a dynamic value for elementId: http://emberjs.jsbin.com/wirahi/1/edit?html,js,output

[rwjblue]

Closing now, as I think my last comment addresses things, but if you can show me where this once worked (which would make this a regression) I'm happy to reopen...