With your plist changes made, start FileMaker back up, and navigate to a layout containing a Web Viewer. You can also try setting the Inspector’s default window mode, however this did not work consistently for us: defaults write 12 "_WebInspectorPageGroupLevel1_.WebKit2InspectorStartsAttached" 1 To avoid this, use the window mode buttons at top-left after the Inspector opens: Quit FileMaker if open (it will overwite the plist change).įor FileMaker Pro 16 Advanced (Yes, advanced12 is correct for version 16): defaults write 12 WebKitDebugDeveloperExtrasEnabled -bool YESįor FileMaker Pro 16 and FileMaker Pro 17/18: defaults write 12 WebKitDebugDeveloperExtrasEnabled -bool YESĪn important caveat with FileMaker 16 however is that the integrated/attached version will cause FileMaker Pro to crash when you quit. Quit any open copies of FileMaker and start up the Terminal app to execute one or more versions of the command below. To do this we need to first enable a hidden option. It turns out if you are using macOS you can get the same facilities found in Safari to debug your code that’s running in a FileMaker Web Viewer. It has been modified to include newer versions of FileMaker, and older references for versions 14 & 15 were removed. Updated for FileMaker 16, 17, 18: This article was originally published July 20, 2015. In comparison, most web browsers have debug facilities that can help developers find problems in their code. If you are having difficulty getting your HTML, CSS, or JavaScript to render in a FileMaker Web Viewer, you may have a struggle ahead of you trying to find the problem, and no good way to debug it.
0 Comments
Leave a Reply. |