Nagarjuna.Borra
17 Sep 2019, 5:11 AM
Hi,
It appears sencha has upgraded the font-awesome version they are using from v4.7.0 to v5.x. I am able to say this by looking at the font css applied on the menu arrow icon. The contents of font-awesome\fonts folder confirm the same.
6.7.0 content: "\f0d7";
font: 16px/1 FontAwesome;
7.0
content: '\f0d7';
font: 16px/1 'Font Awesome 5 Free';
Unfortunately, this created problems for our generated theme which was created with Extjs6.7.0 and Themer1.3.5, after upgrading to Extjs7.0. I see that the arrows for the menus on toolbar controls are still specifying the old font css as - 16px/1 FontAwesome ,as a result the arrow icons are not being shown.
58063
Few questions:
1. So, is there a special process to upgrade a themer package? I thought that - simply opening the existing package on Themer 1.3.6(with Extjs7.0) and generating the css again is enough for upgrade.
2. Assuming there is no special upgrade process, can we treat this as a bug in the themer?
3. For Extjs7.0, are we supposed to use only the latest themer version(i.e 1.3.6) ? or, can we use 1.3.5 too? (If the problem does not happen with v1.3.5, maybe we can use it until the problem is fixed on v1.3.6)
Thank you.
It appears sencha has upgraded the font-awesome version they are using from v4.7.0 to v5.x. I am able to say this by looking at the font css applied on the menu arrow icon. The contents of font-awesome\fonts folder confirm the same.
6.7.0 content: "\f0d7";
font: 16px/1 FontAwesome;
7.0
content: '\f0d7';
font: 16px/1 'Font Awesome 5 Free';
Unfortunately, this created problems for our generated theme which was created with Extjs6.7.0 and Themer1.3.5, after upgrading to Extjs7.0. I see that the arrows for the menus on toolbar controls are still specifying the old font css as - 16px/1 FontAwesome ,as a result the arrow icons are not being shown.
58063
Few questions:
1. So, is there a special process to upgrade a themer package? I thought that - simply opening the existing package on Themer 1.3.6(with Extjs7.0) and generating the css again is enough for upgrade.
2. Assuming there is no special upgrade process, can we treat this as a bug in the themer?
3. For Extjs7.0, are we supposed to use only the latest themer version(i.e 1.3.6) ? or, can we use 1.3.5 too? (If the problem does not happen with v1.3.5, maybe we can use it until the problem is fixed on v1.3.6)
Thank you.