Browse Source

docs: add Faq to popover/popconfirm/dropdown (#1071)

YannLynn 3 years ago
parent
commit
0d35715e59

+ 6 - 0
content/feedback/popconfirm/index-en-US.md

@@ -144,3 +144,9 @@ Please refer to [Use with Tooltip/Popover](/en-US/show/tooltip#Use-with-Popver-o
 | onClickOutSide     | Callback when the pop-up layer is in the display state and the non-Children, non-floating layer inner area is clicked                                                 | (e: event) => void         |                     | **2.1.0**        |
 ## Design Tokens
 <DesignToken/>
+
+## FAQ
+
+- **Why does the Popconfirm floating layer lose its width and wrap unexpectedly when the width is not enough near the screen border?**
+
+    After Chromium 104, the wrapping rendering strategy when the width of the screen border text is not enough has changed. For details, see [issue #1022](https://github.com/DouyinFE/semi-design/issues/1022), the semi-side has been This problem was fixed in v2.17.0.

+ 6 - 1
content/feedback/popconfirm/index.md

@@ -142,4 +142,9 @@ function TypesConfirmDemo(props = {}) {
 | onVisibleChange    | 气泡框切换显示隐藏的回调                                                                                                               | Function(visible: boolean): void | () => {}            | **0.19.0**        |
 
 ## 设计变量
-<DesignToken/>
+<DesignToken/>
+
+## FAQ
+
+-   **为什么 Popconfirm 浮层在靠近屏幕边界宽度不够时,丢失宽度意外换行?**  
+    在 chromium 104 后 对于屏幕边界文本宽度不够时的换行渲染策略发生变化,详细原因可查看 [issue #1022](https://github.com/DouyinFE/semi-design/issues/1022),semi侧已经在v2.17.0版本修复了这个问题。

+ 5 - 0
content/show/dropdown/index-en-US.md

@@ -504,6 +504,11 @@ function DropdownEvents() {
 
 <DesignToken/>
 
+## FAQ
+- **Why does the Dropdown layer accidentally wrap when the width is not enough near the screen border?**
+
+    After Chromium 104, the wrapping rendering strategy when the width of the screen border text is not enough has changed. For details, see [issue #1022](https://github.com/DouyinFE/semi-design/issues/1022), the semi-side has been This problem was fixed in v2.17.0.
+
 <!-- ## Related Material
 
 ```material

+ 4 - 0
content/show/dropdown/index.md

@@ -499,6 +499,10 @@ function DropdownEvents() {
 
 <DesignToken/>
 
+## FAQ
+-   **为什么 Dropdown 浮层在靠近屏幕边界宽度不够时,丢失宽度意外换行?**  
+    在 chromium 104 后 对于屏幕边界文本宽度不够时的换行渲染策略发生变化,详细原因可查看 [issue #1022](https://github.com/DouyinFE/semi-design/issues/1022),semi侧已经在v2.17.0版本修复了这个问题。
+
 <!--
 ## 相关物料
 

+ 3 - 0
content/show/popover/index-en-US.md

@@ -541,3 +541,6 @@ Please refer to [Use with Tooltip/Popconfirm](/en-US/show/tooltip#%E6%90%AD%E9%8
     2. Use the FunctionComponent wrapped by forwardRef to pass props and ref to the real dom node
 
     When Semi Input with prefix is used as children, even if the same width of Input and Popover content are set, the position of the floating card is still positioned relative to the input box that does not contain the prefix part. At this time, just put another div on the outer layer of the children to solve the problem.
+- **Why does the popover layer card lose its width and wrap unexpectedly when the width is not enough near the screen border?**
+
+     After Chromium 104, the wrapping rendering strategy when the width of the screen border text is not enough has changed. For details, see [issue #1022](https://github.com/DouyinFE/semi-design/issues/1022), the semi-side has been This problem was fixed in v2.17.0.

+ 4 - 1
content/show/popover/index.md

@@ -542,4 +542,7 @@ import { Button, Input, Popover, Space } from '@douyinfe/semi-ui';
     1. 真实 dom 节点的 jsx 类型,如 span,div,p...
     2. 使用 forwardRef 包裹后的函数式组件,将 props 与 ref 透传到真实的 dom 节点上
 
-    若以带有前缀的 Semi Input 作为 children,即使设置了 Input 和 Popover content等宽,浮层卡片的位置仍是相对于不包含前缀部分的 input 框进行定位,此时只要在 Input 外层再套一个 div 就能解决问题。
+    若以带有前缀的 Semi Input 作为 children,即使设置了 Input 和 Popover content等宽,浮层卡片的位置仍是相对于不包含前缀部分的 input 框进行定位,此时只要在 Input 外层再套一个 div 就能解决问题。
+
+-   **为什么 Popover 浮层卡片在靠近屏幕边界宽度不够时,丢失宽度意外换行?**  
+    在 chromium 104 后 对于屏幕边界文本宽度不够时的换行渲染策略发生变化,详细原因可查看 [issue #1022](https://github.com/DouyinFE/semi-design/issues/1022),semi侧已经在v2.17.0版本修复了这个问题。