| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[BugFix][Desktop] Support MTS NAPI modules in the embedder - Register view-scoped native and extension NAPI factories with the MTS native module manager while preserving native-module-first lookup priority. - Forward an opaque caller-owned runtime context through generic factory hooks so each view binds its own MTS environment without thread-local state. - Expose only the NAPI surface of extension modules to MTS while keeping all extension lifecycle callbacks on the BTS factory. - Recreate the MTS manager and factories with each shell reset, bind the Lynx view context, and cover extension NAPI invocation and teardown behavior. TEST: Passed the two MTS extension module factory tests, rebuilt the native module manager test objects and macOS libLynx.dylib, passed the keyword checker, and verified with macOS LynxDesktop that MTS invokes the extension NAPI module without extension lifecycle callbacks while the page loads successfully. AutoSubmit: true | 1 个月前 | |
[BugFix][DevTool] Match runtimes to shared JS contexts on Harmony Create a JSVM runtime when reusing a shared JSVM context on Harmony to avoid incompatible runtime initialization. SkipChecks: macro AutoLand: release/4.3 | 13 天前 | |
[Doc] Add AGENTS guides for runtime and renderer bridges - Add AGENTS guides for runtime bridge layers across JS, JSI, LepusNG, profiling, VDOM, Starlight, and TASM React. - Document how these bridging directories hand work between execution engines, renderer trees, and wrapper boundaries. - Verified by keeping this commit within the 300-line limit during the history rewrite. AutoSubmit:True | 6 个月前 | |
[Feature][Runtime] Add js to native call frequency monitor Introduce JsCallNativeFrequencyMonitor to detect excessive JS-to-native calls per method_name within a time window and emit a LynxError when threshold is exceeded. Read enable switch and tuning parameters from LynxEnv (remote config), with devtool mode forcing the monitor on for debugging. Update defaults to a 5000ms window with a more practical threshold to avoid missing issues on high-end devices while keeping false positives low, and trim error context fields while including method_name in the error message. issue: m-6864245629 doc: https://github.com/lynx-family/lynx/discussions/281 AutoSubmit: True | 6 个月前 | |
[Feature] Add JS-call-native frequency monitoring for ContextProxy events Introduce `JsCallNativeFrequencyMonitor` to `ContextProxy::DispatchEvent` when enabled via `LynxEnv`, and emit a warning log when dispatch is invoked too frequently for the same target/origin/type combination. Simplify `JsCallNativeFrequencyMonitor::Record` to derive `now_ms` internally from `CurrentSystemTimeMilliseconds`, updating all call sites issue: m-6864245629 doc: https://github.com/lynx-family/lynx/discussions/281 AutoSubmit: True | 6 个月前 | |
[Feature] Add JS-call-native frequency monitoring for ContextProxy events Introduce `JsCallNativeFrequencyMonitor` to `ContextProxy::DispatchEvent` when enabled via `LynxEnv`, and emit a warning log when dispatch is invoked too frequently for the same target/origin/type combination. Simplify `JsCallNativeFrequencyMonitor::Record` to derive `now_ms` internally from `CurrentSystemTimeMilliseconds`, updating all call sites issue: m-6864245629 doc: https://github.com/lynx-family/lynx/discussions/281 AutoSubmit: True | 6 个月前 | |
[Feature] Add JS-call-native frequency monitoring for ContextProxy events Introduce `JsCallNativeFrequencyMonitor` to `ContextProxy::DispatchEvent` when enabled via `LynxEnv`, and emit a warning log when dispatch is invoked too frequently for the same target/origin/type combination. Simplify `JsCallNativeFrequencyMonitor::Record` to derive `now_ms` internally from `CurrentSystemTimeMilliseconds`, updating all call sites issue: m-6864245629 doc: https://github.com/lynx-family/lynx/discussions/281 AutoSubmit: True | 6 个月前 | |
[Refactor][Runtime] Consolidate JS runtime utilities into js namespace Move JS-related runtime utilities from core/runtime/common into core/runtime/js and update all includes, namespaces, and call sites to use the new layout. Key updates: - Rename and relocate utils, args_converter, and jsi_object_wrapper into core/runtime/js, and drop Android-only helpers from the common layer. - Switch JSErrorReporter and console constants to the lynx::runtime namespace and fix all references (including devtool mappings). - Replace the removed utils_map JNI glue with generic byte-array helpers in Android JNIHelper for JavaOnlyArray/JavaOnlyMap interop. - Update BUILD.gn, JNI configs, and unit tests to reflect the new directory structure and header paths. AutoSubmit: True doc: https://github.com/lynx-family/lynx/discussions/281 issue: m-6787224557 | 8 个月前 | |
[Refactor][Runtime] Consolidate JS runtime utilities into js namespace Move JS-related runtime utilities from core/runtime/common into core/runtime/js and update all includes, namespaces, and call sites to use the new layout. Key updates: - Rename and relocate utils, args_converter, and jsi_object_wrapper into core/runtime/js, and drop Android-only helpers from the common layer. - Switch JSErrorReporter and console constants to the lynx::runtime namespace and fix all references (including devtool mappings). - Replace the removed utils_map JNI glue with generic byte-array helpers in Android JNIHelper for JavaOnlyArray/JavaOnlyMap interop. - Update BUILD.gn, JNI configs, and unit tests to reflect the new directory structure and header paths. AutoSubmit: True doc: https://github.com/lynx-family/lynx/discussions/281 issue: m-6787224557 | 8 个月前 | |
[Refactor][Runtime] Consolidate JS runtime utilities into js namespace Move JS-related runtime utilities from core/runtime/common into core/runtime/js and update all includes, namespaces, and call sites to use the new layout. Key updates: - Rename and relocate utils, args_converter, and jsi_object_wrapper into core/runtime/js, and drop Android-only helpers from the common layer. - Switch JSErrorReporter and console constants to the lynx::runtime namespace and fix all references (including devtool mappings). - Replace the removed utils_map JNI glue with generic byte-array helpers in Android JNIHelper for JavaOnlyArray/JavaOnlyMap interop. - Update BUILD.gn, JNI configs, and unit tests to reflect the new directory structure and header paths. AutoSubmit: True doc: https://github.com/lynx-family/lynx/discussions/281 issue: m-6787224557 | 8 个月前 | |
[Optimize] Centralize console method names and reuse constants Replace hardcoded console method strings across JS, Lepus, MTS runtime, and devtool observer with shared constants from `lynx_console_helper.h`. This reduces duplication and prevents drift between components when adding or renaming console methods. Expand the shared console name set to cover additional console APIs (e.g. `assert`, `count`, `group*`, `time*`, `table`) and update existing bindings/event routing and unit tests to reference the unified names. AutoSubmit: True | 5 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 个月前 | ||
| 13 天前 | ||
| 6 个月前 | ||
| 6 个月前 | ||
| 6 个月前 | ||
| 6 个月前 | ||
| 6 个月前 | ||
| 8 个月前 | ||
| 8 个月前 | ||
| 8 个月前 | ||
| 5 个月前 |