feat(web): use pure DOM API to implement Element PAPIs

[PupilTong]

Note that the web-mainthread-apis releasing is temporarily disabled

1. rewrite all element PAPIs impl. Now we use DOM.
2. use our new package @lynx-js/offscreen-document to support the new Element PAPI implementation in a worker

#51

Summary

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[changeset-bot]

🦋 Changeset detected

Latest commit: f3d89f7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codspeed-hq]

CodSpeed Performance Report

Merging #334 will not alter performance

_{Comparing PupilTong:p/hw/refactor-main-thread-api-for-issue-51 (f3d89f7) with main (797cfe6)}

Summary

✅ 1 untouched benchmarks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[codecov]

Bundle Report

Changes will increase total bundle size by 5.07kB (1.24%) ⬆️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
@lynx-js/web-explorer-web-array-push	413.1kB	5.07kB (1.24%) ⬆️

Affected Assets, Files, and Routes:

view changes for bundle: @lynx-js/web-explorer-web-array-push

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
static/js/index.js	-2 bytes	148.83kB	-0.0%
static/js/async/33.js (New)	92.46kB	92.46kB	100.0% 🚀
static/js/async/93.js (New)	92.46kB	92.46kB	100.0% 🚀
static/js/async/217.js (Deleted)	-89.92kB	0 bytes	-100.0% 🗑️
static/js/async/436.js (Deleted)	-89.92kB	0 bytes	-100.0% 🗑️

[Copilot]

Pull Request Overview

This pull request updates the element PAPIs implementation on the web platform to use pure DOM APIs and integrates the new package (@lynx-js/offscreen-document) for worker support. Key changes include rewriting event, style, and attribute/property functions to operate on native HTMLElements instead of custom element types, revising runtime module loading and exposure service logic, and removing legacy offscreen document utilities.

Reviewed Changes

Copilot reviewed 20 out of 24 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/web-platform/web-constants/src/index.ts	Added an export statement for types from the web-worker-rpc package
packages/web-platform/web-mainthread-apis/src/utils/createExposureService.ts	Implements and revises exposure event handling using native DOM events
packages/web-platform/web-mainthread-apis/src/MainThreadRuntime.ts	Updates runtime configuration and module loading with adjustments to error handling and new symbol definitions
packages/web-platform/web-mainthread-apis/src/elementAPI/*	Rewrites functions to operate on native HTMLElements and removes legacy custom element APIs
packages/web-platform/offscreen-document/src/webworker/OffscreenDocument.ts	Adjusts class inheritance to extend OffscreenNode instead of EventTarget
(Other files)	Various refactors in event handling, style updating, DOM tree operations, and element creation have been performed to align with the new pure DOM API approach

Files not reviewed (4)

• cspell.jsonc: Language not supported
• packages/web-platform/web-mainthread-apis/package.json: Language not supported
• packages/web-platform/web-mainthread-apis/tsconfig.json: Language not supported
• packages/web-platform/web-tests/package.json: Language not supported

Comments suppressed due to low confidence (2)

packages/web-platform/web-mainthread-apis/src/MainThreadRuntime.ts:215

• The empty catch block in __LoadLepusChunk may hide errors during module imports. Consider logging the error or handling it appropriately for debugging.

this.__LoadLepusChunk: (path) => { try { this.lynx.requireModule(path); return true; } catch { } return false; };

packages/web-platform/web-mainthread-apis/src/utils/createExposureService.ts:45

• [nitpick] Using the literal interval value (1000 / 20) directly can reduce clarity. Consider defining a named constant for the interval rate to improve maintainability.

}, 1000 / 20);