Ticket #2530311 (closed defect)
Reporter Ian Henshaw |
Opened: 05/26/11 Last modified: 04/18/12 Status: closed Type: defect Resolution: duplicate Duplicate of: #2530076 |
Owner Satyen Desai |
Target Release: Priority: P3 (normal) |
|---|---|---|---|
| Summary: | contentBox attribute ignored when CONTENT_TEMPLATE === null | ||
| Description: | When a widget has CONTENT_TEMPLATE: null, it ignores the contentBox attribute value passed via config. CONTENT_TEMPLATE is used to create a contentBox when one is not provided, and that by setting it I have just had the scenario where ordinarily, I would not want separate contentBox and boundingBox elements, but in this particular use case, it is required, but I find myself unable to override the I overrode _setCB to define the behaviour I expected. _setCB: function(node) {
|
||
| Type: | defect | Observed in Version: | 3.1.1 |
| Component: | Widget | Severity: | S3 (normal) |
| Assigned To: | Satyen Desai | Target Release: | |
| Location: | Priority: | P3 (normal) | |
| Tags: | widget,contentBox,CONTENT_TEMPLATE | Relates To: | |
| Browsers: | N/A | ||
| URL: | http://korpse.demon.co.uk/yuibugs/2530311/ | ||
| Test Information: | |||
Change History
|
Posted: 06/23/11
|
|
Posted: 09/20/11
|
|
Posted: 09/20/11
|
|
Posted: 09/20/11
|
|
Posted: 04/18/12
|
|
Posted: 04/18/12
I don't think the problem has been addressed, I've added a test url to put forward my case. Sorry for not doing this earlier. |
|
Posted: 04/18/12
This ticket was marked as a duplicate of #2530076 |
|
Posted: 04/18/12
Hmm... sorry, my comments got dropped when I switched it back to "duplicate". Didn't mean to do it without an explanation ... What I added was : 'Yes it is still an open issue. It's just marked "closed" because that happens automatically when I mark it as a duplicate of the other bug, which is in the potential backlog list for 3.6.0' Satyen |
This ticket was marked as a duplicate of #2530076