Per elastic/kibana#89748 (review)

The filter modal is using switches to disable/enable individual filters. As switches should only be used if toggling them has an immediate effect (which is not the case in this modal, "Apply" has to be clicked for something to happen) they should be replaced by checkboxes

<img width="437" alt="Screenshot 2021-03-10

Problem Description

Users can choose to fire webhooks on specific actions and specify a message to be sent with it.

This message can access event properties for the event that triggered the action.

Event properties accessed with event.properties.desired_prop will just be substituted with undefined if the property doesn't exist and the message will send without issues.

However,

When you open page UI Elements -> Cards i see TABS are not showing content until you click on other and back on first, same for pills.

Possible fix : ( worked for me )

<script type="text/javascript"> $(document).ready(function(){ $('.nav-item').tab('show'); $('.nav-tabs li a:first').trigger('click'); }); </script>

What is missing?

I was chatting with @paulfantom and we were thinking of having a first-class field in our top level configuration called platform that applies the respective platform specific patch automatically, instead of people having to understand how to use it in jsonnet.

**Why do we need it

I've been working on the MaterialTemplate and when adding a background color to the "main" area I see the below problem.

This will be a problem as soon as people as a different background color than white.