A Bookmarklet to restore FileMaker WebDirect Toolbar buttons in Chrome 62+
UPDATE: Google Chrome 63 was released on Dec. 6 and this problem is now fixed :-)
Google Chrome 62 was released on Oct. 17, 2017. With it came a situation on some (older?) Macs running El Capitan (OS X 10.11) in which the buttons in the FileMaker WebDirect Toolbar do not appear, even though they still function. UPDATE: FileMaker’s Testing department has been able to reproduce this also in Sierra & High Sierra (macOS 10.12.6 & 10.13), although I haven’t seen that. (link)
I've created a bookmarklet that should restore the button images.
How to create the bookmarklet:
a) Copy the JavaScript code (below) b) Right-click (or hold the “option” key and click) on your Bookmarks Bar in Chrome c) Select “Add Page…” d) Enter a Name for this bookmarklet e) In the URL field paste in the JavaScript f) Click “Save" g) Log into your WebDirect solution and then click your new bookmarklet. (gone are the days when you could just drag a bookmarklet onto your bookmark bar :( )
javascript:(function(){var newcss=".fm-statusarea-container .v-nativebutton, .fm-statusarea-container .v-menubar{background-clip: content-box;}";if("\v"=="v"){document.createStyleSheet().cssText=newcss}else{var tag=document.createElement("style");tag.type="text/css";document.getElementsByTagName("head")[0].appendChild(tag);tag[(typeof document.body.style.WebkitAppearance=="string")?"innerText":"innerHTML"]=newcss}})();
FWIW: The issue seems to be connected to CSS, so the bookmarklet injects some CSS (via JavaScript) so that the buttons are visible again. For whatever reason, the elements that hold the buttons have something weird going on with their background CSS. Using background-clip: content-box; seemed to be the simplest fix, even if it’s not exactly changing the root cause of the problem.
You can see more about the issue and follow for updates at: WebDirect Toolbar buttons no longer display in new Chrome 62 on El Capitan on FileMaker Community.
(The bookmarklet was modified from this one. It might not be the most efficient, but it works ;) )












