I have a page with an edit form on it and this has some RadTextBox and RadNumericTextBox controls. The page uses a master page that has a RadFormDecorator declared on it and is set
to decorate Textbox controls. RadTextBox controls are set to a width of
300px.
The problem i have noticed is that when the page loads and i click a button to show me a edit form (the edit form is set to visible = true) all the RadTextBox controls have a width set to 294px but when i hover over a control its width is resets to 300px. All this makes the form look bad because every time the user hovers over any of the RadTextBox controls it changes its size and changes the look of the form.
All this only hapend if the page uses AJAX to update controls.
If i include an ASP Textbox control on the page an set its width in markup to 300px it renders as 294px when i open my form but it doesn't suffer from the same resizing on hover as the RadTextBox does.
If i change the RadFormDecorator not to decorate Textbox controls the problem goes away and all the TextBox controls are rendered with a width of 300px.
As said the problem appeared when upgrading to Q3 2011 release. If i go back to using Q2 2011 release the problem goes away.
The problem i have noticed is that when the page loads and i click a button to show me a edit form (the edit form is set to visible = true) all the RadTextBox controls have a width set to 294px but when i hover over a control its width is resets to 300px. All this makes the form look bad because every time the user hovers over any of the RadTextBox controls it changes its size and changes the look of the form.
All this only hapend if the page uses AJAX to update controls.
If i include an ASP Textbox control on the page an set its width in markup to 300px it renders as 294px when i open my form but it doesn't suffer from the same resizing on hover as the RadTextBox does.
If i change the RadFormDecorator not to decorate Textbox controls the problem goes away and all the TextBox controls are rendered with a width of 300px.
As said the problem appeared when upgrading to Q3 2011 release. If i go back to using Q2 2011 release the problem goes away.