[Enhancement][SSR]: enable Declarative Shadow Dom usage
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 285
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 59
Description
Feature Request Description
Until know we always create a shadow DOM in the UI5 Element, without anticipating that shadow DOM could exist as a declarative shadow DOM.
This is the first step to enable the whole SSR story, to allow declarative shadow DOM usage.
Proposed Solution
Consider the existence of declarative shadow DOM and does not create our own in this case, that replaces the declarative shadow DOM.
Proposed Alternatives
No response
Organization
No response
Additional Context
No response
Priority
None
Privacy Policy
- I’m not disclosing any internal or sensitive information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating where the UI5 Element creates its shadow DOM and trace how existing declarative shadow DOM is detected. Done means a declarative shadow root is preserved rather than replaced, with coverage for the SSR-related behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100