Describe the bug
In Firefox, the zoom feature uses transform styles (see storybookjs/storybook#12845) - unfortunately this breaks positioning on elements that require position: fixed when in the "Docs" view.

Normally a position: fixed element's position would correspond to the viewport but in Firefox it corresponds to the element with the transform style.

Environment

Vuetify Version: 2.4.3
Vue Version: 3.0.5
Browsers: Chrome 88.0.4324.96
OS: Mac OS 10.15.7

Steps to reproduce

• open the type week sample code by codepend
• set calendar type to custom-daily
• set start=2019-01-05, end=2019-01-10,
• set Thomas Birthday as `start: '2019-01-01', end:

I am currently finding it impossible to test for style changes in a containerViews around the ListItem.Accordion, as RNE only provides access to the containerStyle and no testID in these views.

I currently have container styles updating based on state changes, applicable on both the Listitem.Accordion children container views and the ListItem.Accordion icon. However because the views do not pr

Marko Version: 4.18.4

Details

I use some facebook markup that I let facebook parse from DOM:

      <fb:login-button 
        auto-logout-link="false"
        button-type="continue_with" 
        size="large"
        scope="public_profile,email" 
        use-continue-as="true">
      </fb:login-button>

In my onMount I then let the facebook API do it's thing with th

What problem does this feature solve?

Is it possible to turn off the animation, or change the animation on the form control explanation's animation that occurs here?: https://github.com/NG-ZORRO/ng-zorro-antd/blob/f80a5bbd5755477c63c5d73929bcdfd0d07f2dfd/components/form/form-control.component.ts#L60

The animation that causes the form control explanation doesn't fit in sometimes with the app

🐛 Bug Report

The useSelect hook takes in props th

Is your feature request related to a problem? Please describe.
Right now, you can put markdown in the article but not in the description. This causes people to put links in the bottom even when logically they would be part of the description (e.g. this Space: https://huggingface.co/spaces/Epoching/3D_Photo_Inpainting)

Describe the solution you'd like
Allow markdown and/or HTML in