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
to NULL, I'm asking Widget not to create a contentBox when one is not provided.

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
default contentBox by configuration.

I overrode _setCB to define the behaviour I expected.

_setCB: function(node) {
var contentBox = Y.Node.one(node);
if (!contentBox) {
contentBox = (this.CONTENT_TEMPLATE === null) ? this.get(BOUNDING_BOX) : this._setBox(null, node, this.CONTENT_TEMPLATE);
}
return contentBox;
},

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

Satyen Desai

YUI Developer

Posted: 06/23/11
  • milestone changed to 3.NEXT
  • priority changed to P3 (normal)
  • status changed from new to accepted

Satyen Desai

YUI Developer

Posted: 09/20/11
  • milestone changed from 3.NEXT to 3.5.0

Satyen Desai

YUI Developer

Posted: 09/20/11
  • estimated changed from 0 to 1.5
  • sprint changed to sprint 1

Satyen Desai

YUI Developer

Posted: 09/20/11
  • duplicate changed to 2530076
  • resolution changed to duplicate
  • status changed from accepted to closed

This ticket was marked as a duplicate of #2530076

Ian Henshaw

YUI Contributor

Posted: 04/18/12
  • testurl changed to http://korpse.demon.co.uk/yuibugs/2530311/

Ian Henshaw

YUI Contributor

Posted: 04/18/12
  • milestone changed from 3.5.0
  • resolution changed from duplicate
  • status changed from closed to reopened

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.

Satyen Desai

YUI Developer

Posted: 04/18/12
  • resolution changed to duplicate
  • status changed from reopened to closed

This ticket was marked as a duplicate of #2530076

Satyen Desai

YUI Developer

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