React Native

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.

相关平台

微信小程序

复现仓库

https://github.com/yangxudong-functorz/taro_issues/blob/main/issue1.ts
小程序基础库: 2.17.3
使用框架: React

复现步骤

直接只用 npm run build:weapp, 报错: Module not found: Can't resolve '"},"path":"....../xxx.config.ts"

期望结果

编译成功

🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

When click the link "documentation for configuration steps" in the Zoom plugin settings page in the system console:

Expected: The Zoom plugin docs open in a new tab

Observed: The docs open in the same tab, so the user is forced to leave Mattermost

Note: Please make sure that MM links are opened inside MM (do not open a new browser tab).

If you're interested please comment here and come [

The Overlay component currently fades in extremely fast and does not fade out. It would be nice if the developer could control the fade in and fade out time of the Overlay component.

Current Behavior

the current DrawerItem passes accessibilityState to Link. this is an invalid attribute for role="link"

Expected Behavior

also exclude accessibilityState from Link in the default DrawerItem

all that really needs to be done is add a line under [this line](https://github.com/react-navigation/react-navigation/blob/0fce8eb2a1e682194d574c65f3366f72e23f2

As discussed on CZO, there are currently several ways to mute a topic. We should remove this redundant option from the message three-dot menu.

Reasons to do so:

• It's a topic action, not a message action.
• There are lots of other, more natural ways to do it.
• The message three-dot menu is g

The "src" directory contains a number of JS files that are added to the base copy of RN. It is not a complete source tree itself. Renaming to "patches" would increase clarity of intent, and follow OSS "patch-package" conventions.

I may be reading it completely wrong, but the current way the Screen component decides whether to use a scrollview or not is to check isNonScrolling(preset)

The code:

export function isNonScrolling(preset?: ScreenPresets) {
  // any of these things will make you scroll
  return !preset || !presets[preset] || preset === "fixed"
}

The comment "Any of these things will make yo