Changes between Initial Version and Version 4 of Ticket #11528


Ignore:
Timestamp:
Aug 18, 2010, 2:59:49 AM (10 years ago)
Author:
bill
Comment:

Perhaps the "regression" is merely that TextBox widgets now share the same problems as ValidationTextBox widgets regarding setting the font on IE. That's just the price we paid for changing the TextBox template to place nice with the other form widgets.

In 2.0 we'll keep things simple, desupporting using style="..." as a way to set the font of a *TextBox, and instead tell developers to either set it through a CSS rule, or perhaps have a custom parameter like inputStyle="font: ...".

However, for 1.x maybe the setTimeout() is a good compromise, so that style="..." keeps working in general. Note that the setTimeout() fix won't work if an app does a

var x = new dijit.form.TextBox();

and then sometime later, after the setTimeout() triggers, attaches that TextBox to the DOM. Luckily that's won't occur often.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11528

    • Property Cc Douglas Hays removed
    • Property Owner set to Douglas Hays
    • Property Summary changed from [regression] font-family of TextBox becomes difficult to override in IE to [regression] TextBox: font-family becomes difficult to override in IE
  • Ticket #11528 – Description

    initial v4  
    1 In Dojo 1.5 (as of revision 21560), !TextBox has its font-family style set inline on IE.  This causes enormous potential for custom-CSS-clobbering regressions, especially in the case of !TextBoxes constructed without srcNodeRef.
     1In Dojo 1.5 (as of [21560]), !TextBox has its font-family style set inline on IE.  This causes enormous potential for custom-CSS-clobbering regressions, especially in the case of !TextBoxes constructed without srcNodeRef.
    22
    33To summarize: