| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[add TestCase] Add test cases for the accessible scrollView. Co-authored-by: chenhaoyue<chenhaoyue1@huawei.com> # message auto-generated for no-merge-commit merge: merge chy0616-1 into master [add TestCase] Add test cases for the accessible scrollView. Created-by: qq_41986353 Commit-by: chenhaoyue Merged-by: huangyouhua Description: ## Description Add test cases for the accessible scrollView. ## Changes - added Add test cases for the accessible scrollView. ## Test Plan 1. Open the tester App. 2. Find the accessibility test cases for ScrollViewExample. 3. Open the accessibility mode to read aloud. ## Checklist <!-- Please conduct self inspection according to the following checklist before merging After completing the self check, fill in "x" in [], For example: - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. --> - [ ] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [ ] Does not impact performance, or performance testing has been conducted without degradation. - [ ] Complies with the relevant coding standards. - [ ] Does not involve documentation updates, or the documentation has been updated. - [ ] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [ ] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1178 | 1 年前 | |
fix: values from animated props aren't set correctly after finishing animation with native driver, leading to wrong values in measure. Co-authored-by: Przemysław Sosna<przemyslaw.sosna@swmansion.com> # message auto-generated for no-merge-commit merge: !1287 merge @sosen/animated-props-fix into master fix: values from animated props aren't set correctly after finishing animation with native driver, leading to wrong values in measure. Created-by: PrzemekSosna Commit-by: Przemysław Sosna Merged-by: huangyouhua Description: ## Description When using the native driver for animations that involve layout changes (ie. translateY and other transforms, but not styles such as opacity), because it bypasses Fabric, the new coordinates are not updated so the values returned by measure are incorrect. This was actually fixed on 0.77, so this PR is a cherrypick of "Trigger rerender on animation complete (#37836)" from the upstream RN repository and "fix: values for animated props are not set correctly after display changes to none" from the 0.77 branch. "fix: the infinite loop caused by the error "Animated node with tag xxx does not exist"." (d7083d23e9573c805196f813d5c1051c702e150c) is also cherrypicked, as without that native driver is bugged and after a coupld of animations doesn't work properly. ## Changes - fix: values from animated props aren't set correctly after finishing animation with native driver, leading to wrong values in measure. ## Test Plan Check the code below, after pressing "Measure Box", the height logged should be 100. tsx import React, {useLayoutEffect, useRef} from 'react'; import {TouchableOpacity, View, Text, Animated} from 'react-native'; export default function App() { const scaleValue = useRef(new Animated.Value(0.2)).current; const boxRef = useRef<View>(null); React.useEffect(() => { Animated.spring(scaleValue, { toValue: 1, friction: 3, useNativeDriver: true, }).start(); }, []); const measureBox = () => { boxRef.current?.measure((x, y, width, height, pageX, pageY) => { console.log({x, y, width, height, pageX, pageY}); }); }; useLayoutEffect(() => { measureBox(); }, []); return ( <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center', gap: 40, }}> <TouchableOpacity onPress={measureBox} style={{padding: 10, backgroundColor: '#eee'}}> <Text>Measure Box</Text> </TouchableOpacity> <Animated.View ref={boxRef} style={{ width: 100, height: 100, backgroundColor: 'orange', borderRadius: 8, transform: [{scale: scaleValue}], justifyContent: 'center', alignItems: 'center', }}> <Text>Scaled Box</Text> </Animated.View> </View> ); } ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1287 | 10 个月前 | |
feat(ScrollView): add HarmonyOS-specific flingSpeedLimit property Signed-off-by: luqi <luqi7@huawei.com> | 6 个月前 | |
fix: include attachments in nested text touch targets Co-authored-by: Patryk Fryda<patryk.fryda@swmansion.com> # message auto-generated for no-merge-commit merge: !1879 merge fix/nested-text-attachments-touch into master fix: include attachments in nested text touch targets Created-by: pafry Commit-by: Patryk Fryda Merged-by: huangyouhua Description: ## Description Attachments were excluded from touch target list and fragment rects calculation, creating unresponsive areas. Now all fragments (text and attachments) are included. Two issues are solved: - one character mismatch in fragment's rect calculation when nested text contains attachment, - pressing area above attachment did had no effect ## Changes - fixed nested text attachment touch behaviour ## Test Plan How to test this PR. For example: 1. Open the Tester project 2. Execute the npm run start command 3. Go to Text section 4. Test pass after pressing area above the attachment and pass after pressing the last character ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1879 | 9 个月前 | |
fix: map the accessible prop correctly The accessible prop was mapped improperly. - fixed behavior of the accessible prop - deprecated ArkUINode::setAccessibilityLevel Run test cases added in this PR. - [x] Project compiles and the tester application works. Closes https://gl.swmansion.com/rnoh/react-native-harmony/-/issues/1381 See merge request rnoh/react-native-harmony!1700 Signed-off-by: chenhaoyue <chenhaoyue1@huawei.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add alert three button test Signed-off-by: zichenyang <zichen834194@163.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: the infinite loop caused by the error 'Animated node with tag xxx does not exist'. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: !1698 merge Animated into master fix: the infinite loop caused by the error 'Animated node with tag xxx does not exist'. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description When a looping animation node is deleted, the next animation does not play. The main reason is that getMinAcceptableFrameRate calls getNodeByTag but does not catch errors, causing the system to enter an infinite loop of continuously throwing errors, which in turn prevents the next animation from playing. ## Changes - fixed the infinite loop caused by the error "Animated node with tag xxx does not exist". ## Test Plan 1. Open the Tester. 1. Check AnimatedTest::after the loading animation ends. ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1698 | 11 个月前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix:m_ctx destroyed when using by asyncTask Signed-off-by: wuxujie <yue5063657@163.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
Fix: Add support for handling ArkTS touches for FallbackComponentInstance. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-bindsheet into master Fix: Add support for handling ArkTS touches for FallbackComponentInstance. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description This merge request introduces a fix for issues related to touch event detection in components placed inside ArkTS modal-like elements such as Sheet. Currently, React children placed inside modals (e.g., via .bindSheet in a custom ArkTS component) do not detect touch events correctly. This is because touch event detection relies solely on the CAPI UIInputTouchEvents. However, when an ArkTS component uses a modal, the touch event is detected only on the ArkTS side and is not propagated to the C++. To address this, a new method has been introduced to the ArkTS RNInstance: postTouchEventMessageToCpp. This method accepts the tag of the root touch target component along with a TouchEvent object and forwards them to the C++. The FallbackComponentInstance, used for custom ArkTS components, has been extended to also inherit from the ArkTS observer. This allows it to listen for touch events from ArkTS. When a touch event with the appropriate tag is received, it is dispatched using a modified TouchEventDispatcher, which now handles both CAPI and ArkTS touch events. Another issue with modal-like components is caused by the differences with JS and native component tree hierarchy. Touch events can still be triggered on components inside a Sheet, even after the Sheet is dismissed and no longer visible. From the JS perspective, the modal root component might still appear as a child of other components, leading to unintended touch propagation. To resolve this, a new method isRootTouchTarget() has been added to the touch target interface. Components that serve as root touch targets can override this method. During the search for touchable children, any such root components are excluded from further propagation. This prevents touch events from being dispatched to dismissed or inactive modal components. In order to detect touch events properly in components like.bindSheet touch event must be intercepted on ArkTs side and forwarded to C++ with postTouchEventMessageToCpp, the example usage is presented in ContainerViewWithModal.ets. It important that .onTouch(…) should be placed inside a builder that is passed to .bindSheet, here’s example usage: tsx @Builder myBuilder() { Column(){ ContentSlot(this.ctx.getContentForTag(this.tag)) } .width('100%') .height('100%') .onTouch((event: TouchEvent) => {this.ctx.rnInstance.postTouchEventMessageToCpp(this.tag, event)}) } build() { RNViewBase({ tag: this.tag, ctx: this.ctx }) { Stack(){}.bindSheet(true, this.myBuilder()) } } ## Changes - modified TouchEventDispatcher to handle both CAPI and ArkTS touch events - added postTouchEventMessageToCpp method to rn instance to forward arkTs events to component instances - modified fallbackComponentInstance to handle touch events form ArkTS ## Test Plan 1. Run tester app 1. Open CustomComponentTest 1. Run ContainerViewWithModalTest and check if button in sheet can be clicked ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1601 | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: window jitter after dragging. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-window into master fix: window jitter after dragging. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description When dragging the window on PC, continuously calling updateConstraints triggers repeated page rendering, resulting in window jitter after the drag stops. In this PR, updateConstraints and Dimensions updates are skipped during window dragging, reducing the number of page renders. ## Changes - fixed window jitter after dragging. ## Test Plan 1. Open the Tester. 1. Check DragingWindowExample in DimensionsTest. ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1464 | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: make I18nManagerTM and AppStateTM work properly Co-authored-by: wuxujie<yue5063657@163.com> # message auto-generated for no-merge-commit merge: !1699 merge wxjer_appState into master fix: make I18nManagerTM and AppStateTM work properly Created-by: wu_xujie1 Commit-by: wuxujie Merged-by: huangyouhua Description: <!-- 请在合并之前删除注释代码，以避免将其包含在GIT历史记录中 --> # 描述 <!-- 简要描述PR的目的，例如: 这条PR主要实现metro局域网内远程调试的功能. --> 1.修复AppStateTM获取前后台状态异常 2.修复I18ManagerTM无法应用用户对于allowRTL和forceRTL的修改 # 变更日志 <!-- 列出可包含在变更日志中的要点的主要变更。 不要列出内部更改。请以下列开头来写每个变更点： - added - fixed - deprecated - removed 如果是一条新增属性的变更，则以[added]开头，例如: - [added] FlatList组件新增inverted属性 --> # 测试步骤 <!-- 如何测试这条PR。例如： 1. 打开Tester工程. 2. 执行npm run start命令. ... --> 1.打开tester工程 2.找到AppState和I18Manger的用例 3.运行AppState用例，对应用进行前后台切换，不出现异常 4.运行I18Manger的用例，用例通过，且可以通过切换forceRTL改变布局 # 合入前自检 <!-- 请在合入前根据以下条例进行自检 自检完成后在[ ]内填入"x", 例如： - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 --> - [ ] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [ ] 不涉及性能或已进行性能测试且无性能劣化。 - [ ] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [ ] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1699 | 11 个月前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
feat: support automatic selection of high-density image variants. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-image into master feat: support automatic selection of high-density image variants. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description A requirement has been raised by partners for RNOH to automatically choose optimal images based on pixel density ratios. To address this, we have implemented an automated multi-density image selection feature. Currently, RNOH provides support for four pixel density scale factors: 1x, 2x, 3x, and 4x. ## Changes - support automatic selection of high-density image variants. ## Test Plan 1. Open the Tester. 2. Check the ImageTest. ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1395 | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: Touch events do not respond after long-pressing to close the Modal. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-modalhandler into master fix: Touch events do not respond after long-pressing to close the Modal. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description When the Modal is closed by long-press, the next touch event doesn't work. I checked the behavior on iOS - when closing the Modal, an onPressOut event is triggered, which should be issued by the system. However, the Harmony system doesn't emit this event. My solution is to manually trigger a TouchEnd event. ## Changes - fixed touch events do not respond after long-pressing to close the Modal. ## Test Plan 1. Open the tester App. 1. Check ModalTest. ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1636 | 11 个月前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: url encode check cannot cover encodeURIComponent type # message auto-generated for no-merge-commit merge: merge url_double_encode into master fix: url encode check cannot cover encodeURIComponent type Created-by: zichenyang21 Commit-by: zichenyang Merged-by: openharmony_ci Description: # Why are these changes being made? Currently only decodeURI is used to decode and check if input url has been encoded. However, in some cases, the url is encoded by encodeURIComponent, by using encodeURI, special symbol like: /, and : would not be encoded, while encodeURIComponent would translate them to %252F and %252F. Same process would happen in decode. For example, when input url is: https://api.example.org/v1/qr-generator?url=https%3A%2F%2Fexample.org%2Fuser%2F12345%3Fref%3Dabc%252Fdef%253A decodeURI has output: "https://api.example.org/v1/qr-generator?url=https%3A%2F%2Fexample.org%2Fuser%2F12345%3Fref%3Dabc%252Fdef%253A", which is the same as input. decodeURIComponent has output: "https://api.example.org/v1/qr-generator?url=https://example.org/user/12345?ref=abc%2Fdef:", which is different. if decodeURI has the same output as input for now, double encoding would happen. At the same time, we do encoding on hostname and pathname by encodeURI, and encode params value by encodeURIComponent, so all special symbols could be encoded formally. # Changelog change isEncodedURI, check decodeURI and decodeURIComponent at the same time. change getEncodedURI, parse URL and encode host and pathname using encodeURI, encode params value using encodeURIComponent. Test Plan Run the following demo, log the output uri to see it is not double encoded, and all special symbols are encoded correctly. import React, { useState, useEffect } from 'react'; import { View, Text, Button, ActivityIndicator, StyleSheet } from 'react-native'; const App = () => { const [responseData, setResponseData] = useState(null); const [loading, setLoading] = useState(false); const [error, setError] = useState(null); // The URL with encoded parameters const apiUrl = "https://api.example.org/v1/qr-generator?url=https%3A%2F%2Fexample.org%2Fuser%2F12345%3Fref%3Dabc%252Fdef%253A"; // const apiUrl = "https://api.example.com/search?query={"name"%3A"John"%2C"age"%3A30}" const fetchData = async () => { setLoading(true); setError(null); try { const response = await fetch(apiUrl); if (!response.ok) { throw new Error(HTTP error! Status: ${response.status}); } const data = await response.json(); // Assuming JSON response setResponseData(data); } catch (err) { setError(err.message); console.error("Request failed:", err); } finally { setLoading(false); } }; return ( <View style={styles.container}> <Text style={styles.title}>HTTP Request Demo</Text> <Button title="Send Request" onPress={fetchData} /> {loading && <ActivityIndicator size="large" />} {error && ( <Text style={styles.error}>Error: {error}</Text> )} {responseData && ( <View style={styles.responseContainer}> <Text style={styles.responseTitle}>Response:</Text> <Text style={styles.responseText}> {JSON.stringify(responseData, null, 2)} </Text> </View> )} </View> ); }; const styles = StyleSheet.create({ container: { flex: 1, padding: 20, justifyContent: 'center', }, title: { fontSize: 20, fontWeight: 'bold', marginBottom: 20, textAlign: 'center', }, error: { color: 'red', marginTop: 10, }, responseContainer: { marginTop: 20, padding: 10, backgroundColor: '#f0f0f0', borderRadius: 5, }, responseTitle: { fontWeight: 'bold', marginBottom: 5, }, responseText: { fontFamily: 'monospace', }, }); export default App; See merge request: openharmony-sig/ohos_react_native!749 | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: receive negative offsetY in onScroll during pull to refresh to match iOS And handle touches correctly during pull-to-refresh Co-authored-by: chenhaoyue<chenhaoyue1@huawei.com> # message auto-generated for no-merge-commit merge: !1737 merge 1026 into master fix: receive negative offsetY in onScroll during pull to refresh to match iOS And handle touches correctly during pull-to-refresh Created-by: qq_41986353 Commit-by: chenhaoyue Merged-by: huangyouhua Description: <!-- Please remove all comments before submitting to avoid them being included in merge commit message --> ## Why are these changes being made? By combining scrollview with refresh, there is no top when sliding down ## Changelog <!-- List user-visible changes in a concise manner. Use one of the following verbs in past tense: - added - fixed - deprecated - removed - optimized Include [breaking] prefix for breaking changes --> The sticky element is achieved by obtaining the offset of the refreshNode component and passing it to the scrollview component. ## Test Plan Pass the demo test ## Checklist - [x] pnpm verify command has passed successfully. - [x] No failures occurred in automatic tests on the CONCURRENT TESTER page in the tester app. - [x] No failures occurred in automatic tests on the SEQUENTIAL TESTER page in the tester app. - [x] MR does not include a breaking change or a review has been requested from a Huawei reviewer. See merge request: openharmony-sig/ohos_react_native!1737 | 11 个月前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add TextInput testcase Signed-off-by: zhangyufen <zhangyufen3@h-partners.com> | 7 个月前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
fix: the touch interaction issue between ScrollView and its parent component. Co-authored-by: 谢代荣<xiedairong@huawei.com> # message auto-generated for no-merge-commit merge: merge master-scrollview into master fix: the touch interaction issue between ScrollView and its parent component. Created-by: xiedrsz Commit-by: 谢代荣 Merged-by: huangyouhua Description: ## Description Previously, my understanding of JSResponder was incomplete. Upon comparing with iOS, I found that when a ScrollView's ancestor element becomes the JSResponder, the ScrollView is not allowed to scroll. In iOS, this is achieved through the touchesShouldCancelInContentViewmethod. However, ArkUI does not have a similar method. Here, I implemented it by using m_scrollNode.setEnableScrollInteraction. Therefore, I moved the logic for querying whether an ancestor element is a JSResponder to the ScrollViewComponentInstance. ## Changes - fixed the touch interaction issue between ScrollView and its parent component. ## Test Plan 1. Open the Tester. 1. Check PanResponderTest. 1. Check ScrollViewNestedInGesturesExample. 1. Check NestedScrollingExample. 1. Check ScrollViewNestedInTouchableOpacityTest in TouchableOpacity. ## Checklist - [x] Does not involve incompatible changes; if involved, has been reviewed accordingly. - [x] Does not impact performance, or performance testing has been conducted without degradation. - [x] Complies with the relevant coding standards. - [x] Does not involve documentation updates, or the documentation has been updated. - [x] Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added. - [x] No illegal file inclusions exist, such as images or code. See merge request: openharmony-sig/ohos_react_native!1435 | 1 年前 | |
[Fix] Added accessibility test cases for the TouchableWithoutFeedback component Co-authored-by: chenhaoyue<chenhaoyue1@huawei.com> # message auto-generated for no-merge-commit merge: merge master-0926 into master [Fix] Added accessibility test cases for the TouchableWithoutFeedback component Created-by: qq_41986353 Commit-by: chenhaoyue Merged-by: huangyouhua Description: # 描述 Added accessibility test cases for the TouchableWithoutFeedback component # 变更日志 -无 # 测试步骤 1. 打开Tester工程. 2. 执行npm run start命令. 3. 找到TouchableWithoutFeedback的测试用例入口即可 # 合入前自检 - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [x] 不涉及性能或已进行性能测试且无性能劣化。 - [x] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [x] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1622 | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
feat: add runOnWorkerThread Signed-off-by: 瞿欣 <quxin9@huawei.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
add the Copyright-Notice for HUAWEI Signed-off-by: 木叶纷下 <694161290@qq.com> | 1 年前 | |
[Fix] Added accessibility test cases for the TouchableWithoutFeedback component Co-authored-by: chenhaoyue<chenhaoyue1@huawei.com> # message auto-generated for no-merge-commit merge: merge master-0926 into master [Fix] Added accessibility test cases for the TouchableWithoutFeedback component Created-by: qq_41986353 Commit-by: chenhaoyue Merged-by: huangyouhua Description: # 描述 Added accessibility test cases for the TouchableWithoutFeedback component # 变更日志 -无 # 测试步骤 1. 打开Tester工程. 2. 执行npm run start命令. 3. 找到TouchableWithoutFeedback的测试用例入口即可 # 合入前自检 - [x] 不涉及非兼容性变更；若涉及，已通过相应评审。 - [x] 不涉及性能或已进行性能测试且无性能劣化。 - [x] 符合对应的编码规范。 - [ ] 不涉及文档更新，或已更新了文档。 - [ ] 针对可测试性要求，已增加必要的自测用例、合理的日志记录或Trace信息。 - [ ] 不存在非法的文件引入，包括图片和代码等 - [x] 本PR已经在77分支开启PR或不需要在77分支合入 - 如需合入77分支，PR地址： See merge request: openharmony-sig/ohos_react_native!1622 | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 |