692675 - Allow users to specify panel content directly, not just by URL

Status: RESOLVED WONTFIX

(Add-on SDK Graveyard :: General, enhancement, P3)

Description

[Will Bamberg [:wbamberg]]

Users can specify HTML content for a widget either by referencing a separate file by URL, using 'contentURL', or directly, using 'content'.

But for a panel they must supply the content in a separate file and reference it with a URL, the 'content' option isn't available. This is inconsistent, and means people have to implement a lot more machinery to have simple dynamic content. We should consider supporting 'content' for panels as well as widgets.

Comment 1

[Myk Melez [:myk] [@mykmelez]]

The reason we didn't implement `content` for Panel is that we planned to remove it from Widget.  But we never got around to that (and one could argue that it would have been the wrong thing to do anyway), and at this point we aren't going to do it, since Widget's API is stable and supported, and this change doesn't meet the high bar for breaking it.

Thus it makes sense to add the property to Panel as well, so the APIs are consistent.

Comment 2

[Erik Vold [:erikvold] (please needinfo? me)]

Taking myself off things that I won't be able to get to for awhile.

Comment 3

[Erik Vold [:erikvold] (please needinfo? me)]

Irakli, should we still do this? or deprecate `content`?

Comment 4

[Irakli Gozalishvili [:irakli] [:gozala] [@gozala]]

Given that widget is deprecated on it's own I don't see much value in deprecating `content` field itself. Also given that none of the new APIs have `content` field I think we should just wontfix this.