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

Environment

Mobile

Joplin 2.3.4
Database v39
Android 11
USING BETA EDITOR

Desktop

Joplin 2.3.5 (prod, win32)
Client ID: a4ed20b9be424a1c8c3e5f3cc355c345
Sync Version: 3
Profile Version: 39
Keychain Supported: Yes
Revision: 819af3c
Windows 10

Steps to reproduce

1. Create new note and start typing title manually
2. Press 'return' and continue typing - repeat
   3

There are still lots of places using the string values for channel types rather than refering the constants directly. We should replace all of those.

All the constants are listed in model/channel.go

If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can di

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

Bug report

Description / Observed Behavior

Passing an updated fetcher method to useSWR has no effect. The initial version of the fetcher will be used.

I am passing a fetcher function to useSWR that is updated by applying a new access token.

const [accessToken, setAccessToken] = useState("valid-0");
const fetcher = () => {
  console.log("fetch with token:", accessToken

The "edit" and "delete" buttons in the drafts menu should be right-aligned with the draft timestamp.

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.

We should discuss/consider using baseUrl in our tsconfig so we can change imports like this:

import { Thing } from "../../components/thing"

to this

import { Thing } from "components/thing"

Docs: https://www.typescriptlang.org/tsconfig#baseUrl