Web Components

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.

It's important, I think, if the goal is to communicate that this can replace React in more ways than function.

I have an podcast with episode uploaded to Mixcloud. I also have my music uploaded to Soundcloud. I'd like to see Mixcloud and Soundcloud added as providers with Vime.js

Also I endorse the feature request for playlist.

I plan to use this with an Svelte app.

The semantic dom diff plugin uses some global variables like __mocha_context__ and __snapshot__ which are only available in a karma mocha context. When it's user in other test runners, or karma without mocha, it crashes with an unhelpful message.

We should check for these variables, and throw a helpful error to the user that explains this plugin can only be used in Karma.

All of the various Stylable directives should warn the user when receiving no arguments and at least 1 is expected.

Current status:

at-rules

• - @st-import
• - @st-scope
• - @custom-selector

rules

• - :global()
• - pseudo-states parameters (fixed)
  • [x]

Describe the bug
Flags elements whose role is none or presentation and which cause the role conflict resolution to trigger.

Isolated Example
This issue occurs on slim-arrow-up/slim-arrow-down/pushpin-off etc. Also for slim-arrow-right/slim-arrow-left icon used in FlexibleColumnLayout

Screenshots
<img width="1920" alt="Screen Shot 2021-06-18 at 1 27 02 PM" src="https://user-i

and ensure that all libs are importable via the following browser ESM code.

import('//unpkg.com/lume?module').then(console.log)
import('//cdn.skypack.dev/lume').then(console.log)
import('//jspm.dev/lume').then(console.log)

At the moment they all fail with network errors for various reasons, namely some dependencies aren't in ESM format.

Hi, team,
Now Teams MSAL2 provider only support multi-tenant AAD application according to these docs:

https://docs.microsoft.com/en-us/graph/toolkit/providers/teams-msal2?tabs=ts#creating-an-appclient-id

https://docs.microsoft.com/en-us/graph/toolkit/get-started/build-a-microsoft-teams-sso-tab?tabs=unpkg%2CHTML#creating-an-appclient-id

In some scenario, we can only use single tenant AAD

I'm submitting a ...
[ ] bug report
[ X] feature request
[ ] support request

Current behavior:
Splash screen not showing on iOS

Expected behavior:
Splash screen is showing on iOS, and can be generated through ionic resources

Steps to reproduce:
Launch the application on an iPhone and expect to see a splash screen

Related code:

According to [this article]