So, what’s the solution? The easiest solution is simple: perform thorough testing. This latter issue has the most potential for courting disaster – if you don’t make your field large enough, it can either limit the visibility of a selected value or allow a user to select a value that they can’t even see! The Solution For example, you’ll notice that the line weight of the controls appears differently in each browser and that in Chrome, the values for Ham and Broccoli are shifted almost entirely off the list and out of view. Small differences, sure, but they can have a big impact on your user interface (UI). Here’s how it looks in Safari and Chrome: WebDirect relies on the browser to generate the controls, so not only can the styling look different from FileMaker Pro, it can also look different from one browser to another. In FileMaker Pro, you can specify the color, line weight, and size of Radio Buttons and Checkboxes to your heart’s content, but when you view those same controls in WebDirect, things can look a lot different. Typically, they look something like this: They control the way a user enters data into a field by making them pick from a particular list of values.

Radio Buttons and Checkboxes are field control styles in the FileMaker platform. That’s what Radio Buttons and Checkboxes are like in FileMaker WebDirect.

Have you ever ordered pizza with your favorite topping, but when you get it, they made a mistake? Like, you ordered pepperoni but got pineapple? It’s still pizza, it’s still delicious – but not quite what you wanted, or expected.

Use button bars with checkbox or radio button icons instead of native control styles for the most consistent UI. TL DR: Radio Buttons and Checkboxes can look different from browser to browser in WebDirect.

Buttonbar html css radiobutton