1140636 - CPOWs don't maintain identity for toString

Status: RESOLVED WONTFIX

(Core :: DOM: Content Processes, defect, P3)

Description

[Blake Kaplan (:mrbkap) (inactive)]

Given a CPOW cpow, |cpow.toString !== cpow.toString|.

This isn't an important bug, and patching it would be annoying (we'd need a "holder" object as a second private value on each CPOW, which IMO wouldn't be worth it). But I figured that it'd be useful at least having a bug on this.

Comment 1

[Blake Kaplan (:mrbkap) (inactive)]

Attachment: Test

Here's a test that we can check in sooner rather than later.

Comment 2

[Blake Kaplan (:mrbkap) (inactive)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=48ca686b782b

Comment 3

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/ce40549140ab

Comment 4

[Tracy Walker [:tracy]]

This only a test, a fix is still needed here. Triage still needed.

Comment 5

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/ce40549140ab

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The leave-open keyword is there and there is no activity for 6 months.
:jimm, maybe it's time to close this bug?

Comment 7

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

CPOWs are deprecated, and if I recall correctly the last status update about removing them said that we no longer call methods or access properties on them.  So this is probably WONTFIX, but someone who's actually involved with CPOW removal should confirm.

Comment 8

[Jim Mathies [:jimm]]

(In reply to Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧ from comment #7)
> CPOWs are deprecated, and if I recall correctly the last status update about
> removing them said that we no longer call methods or access properties on
> them.  So this is probably WONTFIX, but someone who's actually involved with
> CPOW removal should confirm.

which is not me. I think felipe might know more about this.

Comment 9

[:Felipe Gomes (needinfo for replies!)]

Yeah, CPOWs are deprecated and only used in tests now. Given this, and that this bug is not too important (as mentioned in comment 0), let's WONTFIX it