TbEditableDetailView::init() set up htmlOptions

[iConn]

change TbEditableDetailView(51)to:

$this->htmlOptions = !isset($this->htmlOptions) 
    ? array('class' => 'table table-bordered table-striped table-hover') 
    : $this->htmlOptions;

Now we can change htmlOptions from $config

[iConn]

Booster 1.1.0

[hijarian]

Hmm, thanks. I'll look whether it's implemented in master or not.

[hijarian]

In master it's line 33, not 51.

Care should be taken about whether to:

• force the four CSS classes listed anyway (so even if you set custom htmlOptions you won't have to remember what classes to put back)
• or use your proposal and overwrite htmlOptions completely with the ones user set (this way any custom property set in htmlOptions, even not related to CSS class, will destroy the predefined styling).

Thank you for finding this line of code, such an attempts to blindly set public properties inside the widget initialization should be avoided.

[digitalcrab]

Hello @iConn thank you for your issue, now it is fixed and committed into the master branch and will be included to the next release.

http://yii-demo.yukki.name/bootstrap/issue684
Here you can find TbEditableDetailView in action and if you will see "issue684-class" css class inside it is mean that everything is OK ;)