Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#8722 closed defect (wontfix)

Bad height with the dojoxRadioView of the Radiogroup

Reported by: Kenny Owned by: dante
Priority: high Milestone: 1.4
Component: Dojox Version: 1.3.0b1
Keywords: RadioGroup Radioview height Cc:
Blocked By: Blocking:


The dojoxRadioView that is the second element of the dojoxRadioGroup after the buttonHolder seems to have a bad height.

The style is 100% height relative of its position.
I don't know why, but it doesn't seem to take into account the buttonHolder to calculate the height.

So when you do a height:100% for the radioGroup children (contentPanes), the layout disappears in the bottom.

The problem appears also here

I use the hasButtons=true property.
With this property to false, the dojoxRadioView has the good height.

Can't it be something re-calculating the height of the view after having inserted the buttons?

Change History (4)

comment:1 Changed 13 years ago by Adam Peller

Owner: changed from Adam Peller to dante

comment:2 Changed 13 years ago by bill

Milestone: tbd1.4

1.3rc1 has been release; bumping remaining tickets to 1.4 (except for documentation/testing tickets)

comment:3 Changed 13 years ago by dante

Resolution: wontfix
Status: newclosed

is this still an issue? there is no test attached isolating the issue or otherwise exposing it. The RadioGroup? will not have Buttons at all in 2.0 (and hopefully just be animated transitions for StackContainer?), so I am hesitant to add any kind of code that takes special consideration for the TabButtons? size (TabContainer? already does this, and RadioGroup? should be merged into StackContainer? rather than be a 'hack')

comment:4 Changed 13 years ago by Kenny

Sorry, but I must say as I had lots of problems with others browsers than FF, that I decided to not use the RadioGroup? anymore (well for the time being).

And, I think you are right. If the buttons are going to disappear in the future version of dojo, then this ticket isn't usefull anymore.

Note: See TracTickets for help on using tickets.