Mehmet Emin Posted March 19 Share Posted March 19 Is there a way to avoid the Chrome page error warnings for the TUniLabel components on the forms, since I don't set/use the attribute 'for'? Thanks Quote Link to comment Share on other sites More sharing options...
Sherzod Posted March 20 Share Posted March 20 14 hours ago, Mehmet Emin said: Is there a way to avoid the Chrome page error warnings for the TUniLabel components on the forms, since I don't set/use the attribute 'for'? Hello, Can you test this approach for now? MainForm.Script -> Ext.define(null, { override: 'Ext.form.Label', afterRender: function () { this.callParent(arguments); if (Ext.isEmpty(this.forId)) { this.getEl().dom.removeAttribute('for'); } } }); Quote Link to comment Share on other sites More sharing options...
irigsoft Posted March 20 Share Posted March 20 34 minutes ago, Sherzod said: Hello, Can you test this approach for now? MainForm.Script -> Ext.define(null, { override: 'Ext.form.Label', afterRender: function () { this.callParent(arguments); if (Ext.isEmpty(this.forId)) { this.getEl().dom.removeAttribute('for'); } } }); thanks, but now this message is shown and again: does this code also apply to hidden TuniLabel ? Quote Link to comment Share on other sites More sharing options...
Sherzod Posted March 20 Share Posted March 20 13 minutes ago, irigsoft said: but now this message is shown Hello, Yes, this is an issue for "for attribute doesn't match any element id". Need to check. 1 1 Quote Link to comment Share on other sites More sharing options...
Mehmet Emin Posted March 20 Author Share Posted March 20 Thanks, it will be great if can be eliminated in next versions. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.