Skip to main content

Fixing FontAwesome for Windows 10

By
I ran into an issue with FontAwesome a few months back, where a NoCache header was being injected at the server and FA was broken for any partial refresh. I convinced the admin to reverse that setting and all was well until last week... We had some users who were not getting any icons to appear. Ever. We tracked it down to a new Windows 10 setting for IE11 which disallows untrusted fonts. Since we do not set security protocols for our users, and there is no chance of ever convincing those admins to change this policy that they explicitly turned on, I had to find a new solution. I did some searching and it turned out to not be too difficult. First, here is the original implementation.
The theme:
<control>
<name>Icon.Search</name>
<property mode="override">
<name>tagName</name>
<value>i</value>
</property>
<property mode="concat">
<name>styleClass</name>
<value>fa fa-search</value>
</property>
</control>
The xsp tag:
<xp:text themeId="Icon.Search" />

Web fonts are out, so I looked for a solution to convert FontAwesome into SVG graphics. It turns out, there is one. Here is the guide I used. This provides you with an SVG image, a CSS class, and a JS file (required for IE). I added those files to my application, and to my theme. Then I modified each icon in the theme as follows:
<control>
<name>Icon.Search</name>
<property mode="override">
<name>tagName</name>
<value>svg</value>
</property>
<property mode="override">
<name>escape</name>
<value>#{false}</value>
</property>
<property mode="concat">
<name>styleClass</name>
<value>icon icon-search</value>
</property>
<property mode="override">
<name>value</name>
<value>&lt;use xlink:href="fonts/symbol-defs.svg#icon-search"&gt; &lt;/use&gt;</value>
</property>
</control>
That essentially solved the issue. The icon alignment can be slightly different as a graphic than as a font, and the appearance is slightly inconsistent. I tried experimenting with the SVG shape-rendering tag without success, but I could have just been doing something wrong or perhaps once the graphic is drawn it won't redraw when the SVG markup changes. Both of those issues are fairly minor in scope.
Labels:

Comments

Post a Comment

Popular posts from this blog

XPages Application Framework (Part 1?)

By
Note: I changed projects and priorities after my last POI article, resulting in a long hiatus. I anticipate using that framework on my current project and will likely refine and complete my related article series. For the past several months, I've been fortunate enough to lead a project overhaul from traditional Domino Webapp to XPages. I had a few goals in mind, but the top three were integrating Bootstrap, embracing MVC principles, and eliminating all SSJS . I imagine the motivation for Bootstrap integration is self-explanatory. There is an OpenNTF project out there called Bootstrap4XPages. I didn't use that for a number of reasons - the main being a policy in the current environment. But you may ask yourself (if you didn't follow that link), why so much hatred for SSJS? I have a litany of reasons. It impacts readability of the XPage source; it hurts maintainability when logic is scattered across dozens of XPages, custom controls, and script libraries; it mixes log...
Post a Comment
Read more

Rows per page selection: Part 1

By
I was asked to create a control that would allow users to select the number of rows per page in a view/repeat control (the application uses both). It seemed simple at first, but I ran into a few issues that I thought I'd share the solutions to. First, lets start at the beginning. I went through the relevant design elements and set row="#{viewScope.tableRows}" , and I created an xp:comboBox with value="#{viewScope.tableRows}" and added items for 20, 30, 50, and 100, and I assigned it an onChange event handler that did a partial execution and partial refresh of a div containing the combo box, pager and the table. Then I started fixing all the problems. Problem 1: The combobox value was a string, but the rows parameter requires an integer. This was causing IllegalArgumentException / java.lang.String incompatible with java.lang.Integer. I added a NumberConverter, but this only slightly changed the exception message to java.lang.Long incompatible with java.lang....
Post a Comment
Read more

Project in Review - Part 3: What didn't work

By
Of course, not everything was an unmitigated success. I tried many things that didn't work out. Much of which I've removed and forgotten about, but a few things remain - either scarred into my psyche or woven too deeply to fix. What didn't work Storing my entire configuration in application.properties Using properties files is great. It let me get configuration out of a profile document and into something much easier to edit - particularly configuration that users will never see or maintain (and thus there is no need for an interface for). But I took it too far. The paths to the other databases are there, and that's good. But view aliases are also there, and that was a mistake. I already have a ViewDefinition enum that describes each view and all the information I need to know about it. I could have set view names there, but instead I'm reading them from the application config. I can change where a view is pointing without having to go into my code. Except of co...
Post a Comment
Read more